Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Issue 914451: Autofill does not respect autocomplete="off"

bugs.chromium.org

Post reply on HN
Print view View original

111–120 of 383 posts

Re: Issue 914451: Autofill does not respect autocomplete="off"

#111

Post by lqet »

carstenhag wrote: post #41

As I had already commented on the issue, it completely breaks Germany's main train ticket selling website: https://i.imgur.com/BjYTgSn.png They have tagged the field as autocomplete=off but Chrome just doesn't care. Also see this linked issue where they collected valid use cases for autocomplete=off. They just seem to ignore 452 use cases (I can't comment on the quality of them, I did not read any). https://bugs.chro…

Can anyone explain why the same behavior does not occur on https://www.sbb.ch/, the Swiss equivalent (which is based on the same software by HaCon)?

E: as soon as you submit a search on sbb.ch, the same problem occurs.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#112

Post by ko27 »

ProfSarkov wrote: post #80
goatinaboat wrote: post #38

Overall, I still believe that neither of the extreme strategies ("always honor autocomplete=off" Is it “extreme” now for a computer to do what the user wants and not what a random Google employee wants? How does this differ from malware?

It's also in the spec. People might not like the spec or it might be incomplete, but adhering to it is a very important part of improving it until it's a good one. Now I'm no webdev, but I could very well imagine that the spec is already a good one. So the situation might be even worse.

No, it's not a requirement in the spec. Chrome is actually spec compliant regarding this issue.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#113

Post by dmix »

VMG wrote: post #46

Autofill for offscreen elements gives me the creeps even without the data getting misinterpreted

This is why form elements should never be hidden after loading. Display none should be the default in the HTML for non-relevant content, which should be enough for most autofillers. It also prevents flashing of content when autofillers try to populate it, causing the hiding to delay, which I recently saw in a production app.

Frameworks like React and Vue don’t even render the HTML into the DOM until conditions are met so the situation is improving.

Another positive step away from jQuery hackery!

Re: Issue 914451: Autofill does not respect autocomplete="off"

#114

Post by obituary_latte »

sandstrom wrote: post #106

This has turned into a sad chicken-race between Google and developers, with lots of innovative workarounds on Stackoverflow. Their tactic of overruling web developers doesn't work, it only make things more complicated for everyone, since many of the workarounds have other negative side-effects. https://stackoverflow.com/questions/12374442/chrome-ignores-... ## Example 1 For a reliable workaround, you can add this cod…

I think it mentioned chrome is even now ignoring ‘display:none’ and ‘visibility:hidden’ declarations so those workarounds no longer work either.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#115

Post by reificator »

nikanj wrote: post #104
ProfSarkov wrote: post #80

Earlier quoted context omitted.

It's also in the spec. People might not like the spec or it might be incomplete, but adhering to it is a very important part of improving it until it's a good one. Now I'm no webdev, but I could very well imagine that the spec is already a good one. So the situation might be even worse.

The spec only says "should", not "must". Apparently these wingnuts thought that means the spec can be ignored.

> The spec only says "should", not "must". Apparently these wingnuts thought that means the spec can be ignored.

Not arguing in favor of this particular choice, but yes. That is exactly what "should" means in most cases.

For instance, in RFC 2119: https://tools.ietf.org/html/rfc2119

> SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#116

Post by ko27 »

nikanj wrote: post #104
ProfSarkov wrote: post #80

Earlier quoted context omitted.

It's also in the spec. People might not like the spec or it might be incomplete, but adhering to it is a very important part of improving it until it's a good one. Now I'm no webdev, but I could very well imagine that the spec is already a good one. So the situation might be even worse.

The spec only says "should", not "must". Apparently these wingnuts thought that means the spec can be ignored.

There are no semantics to discuss. Chrome is spec compliant. That's a fact. Words like "should" and "must" have well defined meaning that is clarified in every spec document, which I would highly advise you to read before writing any further comments and insults.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#117

Post by TeMPOraL »

sky_rw wrote: post #98
Nitramp wrote: post #94

Earlier quoted context omitted.

It's called "user agent", not "developer's agent". We'd be in a terrible situation if the browsers just followed developer's whims. Cf. popup blocking.

Dismissing the above use cases as "developer's whims" is the fundamental issue most people here are taking with these decisions. I think we can all agree that browser behavior should not be left solely up to the developer and is not a black and white issue. Nobody here is arguing that. We are arguing for following a guideline that makes sense. This is why we have the w3c, an organization that attempts to weigh the ne…

The issue is that the browser is supposed to be the meeting place for negotiating between developer and user preferences. Its job is to take into account preferences of both sides, and render the site accordingly. Not to be a third party at the negotiating table. Breaking agreed standard in a way that can't be overridden by the user? Browsers should never do that.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#118

Post by isostatic »

ss3000 wrote: post #87

Setting aside the merits/lack-thereof of this particular decision, Chromium ignoring established web standards like this is especially dangerous as we're trending towards a world where 1) Chromium itself powers the most popular browser in the world by an increasingly unhealthy margin, and 2) even competing browsers are increasingly becoming skins on top of Chromium. We are becoming more and more reliant on the develo…

It’s heresy on HN to suggest that a single browser running the web is a bad idea.

Re: Issue 914451: Autofill does not respect autocomplete="off"

#119

Post by [deleted] »

obituary_latte wrote: post #110
ko27 wrote: post #101

Earlier quoted context omitted.

Strictly speaking, Chrome is not ignoring a web standard, since the standard does not require this behavior (no "MUST" keyword).

Well they are ignoring hundreds if not thousands of developers which is the main issue at this point.

[deleted]

Re: Issue 914451: Autofill does not respect autocomplete="off"

#120

Post by subroutine »

lqet wrote: post #111
carstenhag wrote: post #41

As I had already commented on the issue, it completely breaks Germany's main train ticket selling website: https://i.imgur.com/BjYTgSn.png They have tagged the field as autocomplete=off but Chrome just doesn't care. Also see this linked issue where they collected valid use cases for autocomplete=off. They just seem to ignore 452 use cases (I can't comment on the quality of them, I did not read any). https://bugs.chro…

Can anyone explain why the same behavior does not occur on https://www.sbb.ch/ , the Swiss equivalent (which is based on the same software by HaCon)? E: as soon as you submit a search on sbb.ch, the same problem occurs.

Did you try using a first-letter of a location you commonly use in forms? Here is what mine looks like when I use 'm' (like OP):

https://i.imgur.com/NlzVqhT.png

and here's what it looks like when I enter 's':

https://i.imgur.com/1u4Iy7S.png

(actually, S does not autocomplete in the Swiss site)

Post reply on HN