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

181–190 of 383 posts

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

#181

Post by klmr »

watwut wrote: post #82
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…

Imo, valid use case for autocomplete=off is "the developer of webapp wants it". Literally that and nothing more.

Unfortunately a few developers are morons who misuse features, and browser vendors try hard to work around them. Case in point, lots of websites used to put `autocomplete="off"` on password boxes, which breaks some password managers. IIRC that’s why Chrome (and other browsers) decided to sometimes ignore the `autocomplete` attribute in the first place. Of course that doesn’t justify ignoring it completely (just for password fields) but maybe a similar reason is at play.

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

#182

Post by megous »

Geeflow wrote: post #67

As a user, Chrome's autocomplete went down the drain for me once they started to fill all fields at once. I tried to autocomplete one field and often chrome filled the other fields with unfitting data. This happened so often that I started to manually complete fields even if autocomplete was available. I still miss the good old times[tm] of single-field autocomplete... (And for the record: As a developer, I have been…

Yup, I like how FF does it. I basically just do a repeated sequence of:

TAB -> Arrow Down (select one of the previously filled values I've used) -> Enter

When filling a form. Given that sometimes we order things on made up names, it's quite useful no to have that autofilled when we're not wanting to.

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

#183

Post by vidarh »

tus88 wrote: post #169
haasted wrote: post #60

Earlier quoted context omitted.

The story might easily be worth that in marketing for Firefox.

I really want to know what the flagged comment said now.

You can see dead/flagged comments by going to your settings page and setting "showdead" to yes.

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

#184

Post by fuzzy2 »

jrockway wrote: post #174
obituary_latte wrote: post #110

Earlier quoted context omitted.

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

By ignoring "hundreds if not thousands of developers" they are respecting the wishes of millions of end-users that don't want the site owner to decide what they can and can't autofill. Obviously a simple boolean is the wrong design here. But can you suggest a better one?

I don't think "millions of end-users" want broken websites because now another developer (Google) gets to decide what's correct (instead of the web dev).

A better solution could be to just behave reasonably by default but allow the user to re-enable auto-fill with a single click.

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

#186

Post by dustinmoris »

httpsterio wrote: post #176
doctorpangloss wrote: post #43

Earlier quoted context omitted.

Disabling autocomplete is so incredibly frustrating that I ran an extension in Safari to remove the off tag from sites. Of course I want to use KeyChain, the whole point is that touch based ID is more secure.

Touch based are not better. Your fingerprint is not a password, it's just an identifier and shouldn't be treated as a secret.

> Your fingerprint is not a password

Correct, because a fingerprint makes a password to some extent redundant.

> it's just an identifier and shouldn't be treated as a secret

Correct, identifiers are not secrets. Your face is not a secret and your fingerprint either. The problem is that we use secrets to identfy someone, when we potentially already have tech which can identify someone without having to remember a secret and store it in a dictionary of secrets on someone else's computer in the cloud.

The sole purpose of a password is to identify someone with a certain degree of confidence. If a fingerprint taken from a handheld device, which has already been proven to belong to a person, can provide the same if not even a higher level of certainty about someone's identy, then a password or as you say "secret" is not required at all anymore.

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

#187

Post by andrewstuart »

jefftk wrote: post #179
andrewstuart wrote: post #89

The weird thing is that there's other teams within Google who offer autocomplete libraries that simply don't work because Chrome overlays it's own autocomplete on top. The maps team seems to have given up on trying to resolve that. Chrome team have made a judgement that autocomplete is required and no-one - not even other teams within Google are allowed to override that functionality. It's weird.

> not even other teams within Google are allowed to override that functionality Isn't that how things should work? If other teams within Google had a special way to override autocomplete wouldn't that be worse? (Disclosure: I work at Google)

My point is that this decision from the Chrome team even breaks Google's own software.

This emphasises the craziness of the unilateral decision by the Chrome team which is essentially saying: "we, the Chrome team are correct and everyone else can go jump in the lake".

I'm not suggesting that Google should have secret special ways to do things.

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

#188

Post by obituary_latte »

jrockway wrote: post #174
obituary_latte wrote: post #110

Earlier quoted context omitted.

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

By ignoring "hundreds if not thousands of developers" they are respecting the wishes of millions of end-users that don't want the site owner to decide what they can and can't autofill. Obviously a simple boolean is the wrong design here. But can you suggest a better one?

Surely there’s a way to check if a field has some kind of programatic interaction like typeahead. Maybe check for that before taking over with autofill? I don’t know - maybe that would break spec or something - I’m not a browser developer. I just know the pain of autocomplete=“off” not working as expected.

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

#189

Post by chrismorgan »

jjcm wrote: post #171
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…

This isn't even the first time we've seen this either. Both Chrome Mobile and Safari Mobile go against the standard and implement `vh` incorrectly. Honestly it seems strange that they go against the standard though considering how much power they have in defining it. Why break from the standard when you can just update the standard. It ends up being the worst of both worlds - documentation that says one thing (that t…

Admittedly, the viewport units are just all-round badly thought out and fundamentally broken. (The corresponding problem with vw is that the viewport units includes viewport scrollbars, so that on a page with vertical scrolling, `width: 100vw` will cause horizontal scrolling on platforms where the scrollbars take space.)

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

#190

Post by dustinmoris »

avellable wrote: post #147

With the new direction chrome is going I wouldn't mind putting "works best on anything but Chrome" on my next web project.

I was thinking the same, websites should just have a big popup somewhere saying that the website might not work on Google Chrome, because it is W3C compliant and Google Chrome doesn't implement W3C standards, whith links to download alternatives browsers.
Post reply on HN