3 ms·
This has nothing to do with making event listeners passive by default. If you don’t do feature detection then of course your website will not be backwards compa
by deno 9y ago
This has nothing to do with making event listeners passive by default. If you don’t do feature detection then of course your website will not be backwards compatible.
If you care about backward compatibility there exists a polyfill for this functionality.
- falcolas 9y agoIn saying that "Devs assume Chrome", I'm asserting that they do not do feature detection. However, that does not absolve Chrome of breaking backwards compatibility, workaround or not. Tossing the responsibility of dealing with their breaking changes back on the developer (with little notice) is what caused this article in the first place.
- deno 9y agoIf Chrome shipped with opt-out UI option to disable janky scrolling, would it be any better? Web is not a static target. Being afraid to break things gets you a decade of Flash websites. Things that are important will be maintained, and things that aren’t… well good riddance. Personally, I think we are way past due HTML6. A sort of Vulkan-like platform for Web[1]. HTML5 should be build on top of this next-gen low level platform. That’s the way forward if Web wants to remain competitive. Otherwise in 5 years we’ll all be writing Android Instant apps. [1] https://github.com/extensibleweb/manifesto https://github.com/extensibleweb/manifesto