<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dasil003</author><text>Take it up with the standards body then.&lt;p&gt;Presumably this came about because some framework or something started including bad default attributes, and then Chrome responds by ignoring the meaning of the specification in order to &amp;quot;improve UX&amp;quot;.  But in the end what happens is that the specification becomes meaningless and we&amp;#x27;re back to the browser wars where you have no way of knowing how anything works except a continuous testing process to vet the veracity of the spec for any browser you are targeting, and of course this is subject to change on a whim by Google.&lt;p&gt;Will it improve the UX?  Maybe... if Google is correct in its unilateral assumptions.  But one thing for sure is that as a developer this costs you time, and it hurts the most if you are a well-intentioned developer who is trying to make the correct choice for your specific use case.</text><parent_chain><item><author>raldi</author><text>Good. It&amp;#x27;s my browser. I get to turn its features on and off, not you.&lt;p&gt;And that goes double on my phone.&lt;p&gt;As a compromise, I&amp;#x27;d accept a prompt like:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    +---------------------------------------+
    |    This page recommends we disable    |
    |    autocomplete. What do you think?   |
    |[Okay] [Fuck them; autocomplete anyway]|
    +---------------------------------------+&lt;/code&gt;&lt;/pre&gt;</text></item></parent_chain></comment><story><title>“autocomplete=off is ignored on non-login input elements”</title><url>https://bugs.chromium.org/p/chromium/issues/detail?id=468153#c164</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jobead</author><text>If you want to &amp;quot;turn it&amp;#x27;s features on and off&amp;quot;, then why does the Chromium team&amp;#x27;s stance of &amp;quot;extensions are the standard way to enable custom behavior&amp;quot;[0] not apply here???&lt;p&gt;This is a classic unfortunate case of using data from the masses to drive a bad design choice because it increases &amp;quot;usage&amp;quot; along an arbitrary axis.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11729287&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11729287&lt;/a&gt;</text><parent_chain><item><author>raldi</author><text>Good. It&amp;#x27;s my browser. I get to turn its features on and off, not you.&lt;p&gt;And that goes double on my phone.&lt;p&gt;As a compromise, I&amp;#x27;d accept a prompt like:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    +---------------------------------------+
    |    This page recommends we disable    |
    |    autocomplete. What do you think?   |
    |[Okay] [Fuck them; autocomplete anyway]|
    +---------------------------------------+&lt;/code&gt;&lt;/pre&gt;</text></item></parent_chain></comment><story><title>“autocomplete=off is ignored on non-login input elements”</title><url>https://bugs.chromium.org/p/chromium/issues/detail?id=468153#c164</url></story>