Chrome breaks the Web
> they made all top-level event listeners passive by default. They call it “an intervention”.<p>This is my very problem with Chrome/Chromium right now. The Chrome team does assumption on how things "should" be (in a highly subjective way) and breaks the web.<p>Another example: they decided to ignore the value of `autocomplete` attributes on `<form>` tags [1], because:<p>> The tricky part here is that somewhere along the journey of the web autocomplete=off become a default for many form fields, without any real thought being given as to whether or not that was good for users. This doesn't mean there aren't very valid cases where you don't want the browser autofilling data (e.g. on CRM systems), but by and large, we see those as the minority cases. And as a result, we started ignoring autocomplete=off for Chrome Autofill data.<p>Problem: Chrome now auto-fills wrong parts of forms with username/passwords and this breaks forms that get unexpected data when submitted. And now, they opened an issue on their tracker [2] to track "Valid use cases for autocomplete=off".<p>This is insane to think that the developer is wrong to use some attributes values, and to assume how a page should behave, ignoring devs intentions and Web standards.<p>[1] <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=468153#c164" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=468153...</a><p>[2] <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=587466" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=587466</a>