2 ms·
>and for those users in that moment things might be worse, but it is making the web better for significantly more people, What are you basing this on?
by ksk 9y ago
>and for those users in that moment things might be worse, but it is making the web better for significantly more people,
What are you basing this on?
- Klathmon 9y agoI explained this in my first comment, but I'm also basing it on my own testing in february when this came out, as well as from user feedback for years from users of mobile safari which has done this for quite a long time and it has greatly improved the scrolling performance in their browser.
- ksk 9y agoBut how does this apply to the majority of users as you suggest? As a user, I'd like the website to keep working. I don't agree with simply breaking working websites via a top-down dictatorial approach.
- Klathmon 9y agoBecause in my personal case a majority of users would take smoother scrolling over a small UI bug that doesn't impact the usability of the application which is fixable in a few hours at most. Because any websites that need this "blocking events" functionality can opt-in to it quite easily. Because as I explained in my first comment, the breakages didn't affect that many websites, and the sites it did affect were mostly just small UI bugs that didn't impact usability. Yes, some sites were impacted and broken, but they were the extreme minority, and even if you accounted for all of the users of all of those sites I'd be willing to bet that it doesn't come anywhere close to being a "majority" of web users. Hell I'd wager that it's not even close to 1% of web users that were negatively impacted by this change in any way.
- ksk 9y agoSorry, I am not convinced with your arguments. Anyway, have a nice day.