<story><title>Chrome breaks the Web</title><url>http://tonsky.me/blog/chrome-intervention/</url></story><parent_chain><item><author>saas_co_de</author><text>&amp;gt; does assumption on how things &amp;quot;should&amp;quot; be (in a highly subjective way)&lt;p&gt;They claim they are making these decisions based on user data which I have no reason to doubt.&lt;p&gt;&amp;gt; and breaks the web.&lt;p&gt;Breaks crap websites that are broken already from performance and usability perspective.&lt;p&gt;I personally think this is exactly what is needed to make the web better as a whole.&lt;p&gt;Individual developers working for individual companies are rarely if ever thinking about the good of their users, except in a very narrow profit motivated sense, and never thinking about the good of the ecosystem as a whole.&lt;p&gt;Google is also &amp;quot;breaking the web&amp;quot; by not auto playing videos, not allowing alerts in one tab to block the entire browser, etc. Those all seem like good things to me.</text></item><item><author>KeitIG</author><text>&amp;gt; they made all top-level event listeners passive by default. They call it “an intervention”.&lt;p&gt;This is my very problem with Chrome&amp;#x2F;Chromium right now. The Chrome team does assumption on how things &amp;quot;should&amp;quot; be (in a highly subjective way) and breaks the web.&lt;p&gt;Another example: they decided to ignore the value of `autocomplete` attributes on `&amp;lt;form&amp;gt;` tags [1], because:&lt;p&gt;&amp;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&amp;#x27;t mean there aren&amp;#x27;t very valid cases where you don&amp;#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.&lt;p&gt;Problem: Chrome now auto-fills wrong parts of forms with username&amp;#x2F;passwords and this breaks forms that get unexpected data when submitted. And now, they opened an issue on their tracker [2] to track &amp;quot;Valid use cases for autocomplete=off&amp;quot;.&lt;p&gt;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.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=468153#c164&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=468153...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=587466&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=587466&lt;/a&gt;</text></item></parent_chain><comment><author>notjoemama</author><text>Woah woah woah. Let me recount&amp;#x2F;nutshell the crux of conversations I&amp;#x27;ve had with my product manager(s) about things like this.&lt;p&gt;Me: Hey, I&amp;#x27;d like to add a work-item to our current sprint that reworks semantic attributes into our site.&lt;p&gt;Them: What would that do?&lt;p&gt;Me: It improves the underlying architecture making the markup more usable and extensible.&lt;p&gt;Them: How does that benefit the users?&lt;p&gt;Me: Over time it will reduce the TTM for features and allows us to adopt a common standard others use on the web.&lt;p&gt;Them: So there&amp;#x27;s no UI and it won&amp;#x27;t affect their workflow?&lt;p&gt;Me: Well, no.&lt;p&gt;Them: Then why would you suggest it? We don&amp;#x27;t have the budget to add meaningless development tasks.&lt;p&gt;I might be biased towards thinking there are &lt;i&gt;plenty&lt;/i&gt; of developers and engineers out there thinking about this stuff but we don&amp;#x27;t always get the final say in what is done. Also, a lot of enterprise applications were and continue to be around before many of these standards. It&amp;#x27;s a struggle to improve what doesn&amp;#x27;t directly add to the bottom line.</text></comment>
<story><title>Chrome breaks the Web</title><url>http://tonsky.me/blog/chrome-intervention/</url></story><parent_chain><item><author>saas_co_de</author><text>&amp;gt; does assumption on how things &amp;quot;should&amp;quot; be (in a highly subjective way)&lt;p&gt;They claim they are making these decisions based on user data which I have no reason to doubt.&lt;p&gt;&amp;gt; and breaks the web.&lt;p&gt;Breaks crap websites that are broken already from performance and usability perspective.&lt;p&gt;I personally think this is exactly what is needed to make the web better as a whole.&lt;p&gt;Individual developers working for individual companies are rarely if ever thinking about the good of their users, except in a very narrow profit motivated sense, and never thinking about the good of the ecosystem as a whole.&lt;p&gt;Google is also &amp;quot;breaking the web&amp;quot; by not auto playing videos, not allowing alerts in one tab to block the entire browser, etc. Those all seem like good things to me.</text></item><item><author>KeitIG</author><text>&amp;gt; they made all top-level event listeners passive by default. They call it “an intervention”.&lt;p&gt;This is my very problem with Chrome&amp;#x2F;Chromium right now. The Chrome team does assumption on how things &amp;quot;should&amp;quot; be (in a highly subjective way) and breaks the web.&lt;p&gt;Another example: they decided to ignore the value of `autocomplete` attributes on `&amp;lt;form&amp;gt;` tags [1], because:&lt;p&gt;&amp;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&amp;#x27;t mean there aren&amp;#x27;t very valid cases where you don&amp;#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.&lt;p&gt;Problem: Chrome now auto-fills wrong parts of forms with username&amp;#x2F;passwords and this breaks forms that get unexpected data when submitted. And now, they opened an issue on their tracker [2] to track &amp;quot;Valid use cases for autocomplete=off&amp;quot;.&lt;p&gt;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.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=468153#c164&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=468153...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=587466&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=587466&lt;/a&gt;</text></item></parent_chain><comment><author>KeitIG</author><text>Talking from the developer point of view here, not the user&amp;#x27;s: I&amp;#x27;m expecting things to be working the same way they are documented in the manual.&lt;p&gt;The changes some browsers have made to autoplay videos or alerts do not contradict what is in the manual.</text></comment>