Chrome breaks the Web
&gt; they made all top-level event listeners passive by default. They call it “an intervention”.<p>This is my very problem with Chrome&#x2F;Chromium right now. The Chrome team does assumption on how things &quot;should&quot; be (in a highly subjective way) and breaks the web.<p>Another example: they decided to ignore the value of `autocomplete` attributes on `&lt;form&gt;` tags [1], because:<p>&gt; 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&#x27;t mean there aren&#x27;t very valid cases where you don&#x27;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&#x2F;passwords and this breaks forms that get unexpected data when submitted. And now, they opened an issue on their tracker [2] to track &quot;Valid use cases for autocomplete=off&quot;.<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:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=468153#c164" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=468153...</a><p>[2] <a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=587466" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=587466</a>