5 ms·
It also means worse accessibility, less introspection, automation, worse/impossible adblocking, etc.
by gf000 2y ago
It also means worse accessibility, less introspection, automation, worse/impossible adblocking, etc.
- vbezhenar 2y ago> worse/impossible adblocking Obviously that's not a downside from a software developer perspective.
- robin_reala 2y agoI’m a software developer, and it seems like a positive to me? Why wouldn’t you want the ability to post-facto manipulate with script the interfaces you are presented with?
- ncruces 2y agoAs long as someone else is paying the bills.
- tcfhgj 2y agowhich ads are all about, someone else paying devs to manipulate their users into buying stuff from someone else
- vbezhenar 2y agoBecause if I added ads to my application, I want those ads to be shown to user, so I can have my money.
- robin_reala 2y agoI think this we’ve discovered the inflection point between the traditional hackers and the SV growth hackers that HN tries to court both of.
- Timwi 2y agoWhat you mean is from a capitalist perspective. Not all software developers are focused on exploiting their users.
- vbezhenar 2y agoFor applications developed by communist developers, it matters not if ads could be blocked or not. I also would argue that extensibility adds overhead to support. For example I had issue with one website where user reported that they can't see some function which clearly was there. Turned out that their adblock mistakenly removed that element because of some generic CSS class name. I'd prefer for user to receive my application in the way I planned it, not in the altered way.
- atoav 2y agoSelecting text can be useful, but it can also become its own usability problem. I recently created a touch interface using a websocket/browser based stack and one of the problem was that users kept selecting the text on buttons because they expected some action while holding the button.
- iknowstuff 2y agohttps://caniuse.com/user-select-none https://caniuse.com/user-select-none + pointer-events + touch-action : )
- laszlokorte 2y agoI currently have the same issue while building a canvas web app. Safari shows a small magnifier glass on double tap/long press and none of the css properties will suppress it.
- GranPC 2y agoI think you can work around it by listening on the touchstart event on your element and calling e.preventDefault(). Don't have an iPhone handy to test it right now, but I believe that's how I fixed that issue in my web game.
- laszlokorte 2y agoThank you for the suggestion. This is also what is discussed in some stackoverflow threads on that topic. I simply do not get why javascript is required to stop the browser from interfering with user actions. Calling preventDefault also messes with element focus and other events.
- GranPC 2y agoYeah, I am not the biggest fan of iOS Safari because of things like these. In my case, disabling most default interactions was a desirable property because I wanted to handle all the UI myself - but I understand that may not always be a good solution.