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

311–320 of 383 posts

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

#311

Post by paulryanrogers »

dustinmoris wrote: post #283
Santosh83 wrote: post #256

Earlier quoted context omitted.

> And using any of these (ideally) has absolutely nothing to do with anonymity. You are not anonymous online regardless of what you use for authentication - and you are frankly not smart if you assume thats the case. A company offering a service with biometrics is no different from a company doing the same based on email/username and a password, if they do privacy and security right. Why should I use unchangeable, pe…

You don't have to identify yourself with a "random Joe's website". You can read the comments here without identification, you can seach for flights without identifying yourself, you can search for hotels without giving away who you are, you can read the news, watch YouTube, etc. But when you want to access something that should only belong to you, e.g. your bank account, your Google Drive files, your private emails,…

Biometrics are digital interpretations, which can be copied. The biological sources cannot be easily changed. So _when_ the digital copies leak they become a liability.

Passwords can be easily changed. And until reliable, remote, mind reading technology becomes available they'll continue to be better than biometrics.

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

#312

Post by Scoundreller »

sedatk wrote: post #305
romaaeterna wrote: post #18

A few years ago, I left a $1000 tip at the restaurant up the street because Chrome filled out the tip field with my zip code (which thankfully merely defaulted to max $1000 instead). The tip field was off-screen, and the ordering software didn't have a confirmation screen, just a "we just charged your card $X amount" screen, which made my eyes boggle. EDIT: Looking at the original March 17th, 2015 bug, it would have…

How do you pay with Chrome at a restaurant?

Probably for pickup or delivery.

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

#313

Post by kalleboo »

rhizome wrote: post #303
kalleboo wrote: post #228

Earlier quoted context omitted.

Password managers should ignore autocomplete=off in login screens, but not in administration screens where you’re editing other people’s credentials. IMO the distinction could be made to not automatically fill when the autocomplete=off but instead add a button to let the user initiate it

> not in administration screens where you’re editing other people’s credentials ...

That was recommended by Google 3 years ago, but there are a bunch of reports in the bug reporter thread that that doesn’t work now. And credentials go beyond passwords - names, usernames, ID numbers

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

#314

Post by platypii »

Thank you chrome, for recognizing that the USER is what matters, not the website developer. Websites started blocking legitimate uses of autocomplete, and that makes the web less secure. As a user I sincerely hope that "autocomplete=off" dies just like the blink tag, as it is user hostile.

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

#315

Post by basch »

subroutine wrote: post #298
basch wrote: post #273

Earlier quoted context omitted.

does the escape key close the extra context menu?

Yeah! Good to know. Did the chrome UI make us aware of that shortcut at some point?

I discovered it during a panic once, never saw it mentioned anywhere.

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

#316

Post by Gibbon1 »

danso wrote: post #242
rc_mob wrote: post #239

Earlier quoted context omitted.

I still don’t understand why any self respecting developer would use Chrome. I understand why your grandma or parents would use Chrome. But I just cannot compute how a knowledgeable developer would install Chrome.

Because Chrome has 70% of the global market share, and web developers should know what their customers use?

Developers need to understand this is war and act accordingly.

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

#317

Post by the_pwner224 »

kps wrote: post #291
Reelin wrote: post #95

Earlier quoted context omitted.

It's complicated. Sometimes website authors do silly things that negatively impact users; browsers ought to help (without breaking things!) where possible. Some daily annoyances that I wish browsers would actively mitigate, in no particular order: js-based redirects, blocking copy-paste, disabling text selection, hijacking the forward slash to open the website's own search function (I'm looking at you, Github), hijac…

In Firefox, shift+right-click brings up the browser context menu.

Arrgh. I wish shortcuts like this were more discoverable. Shift+right click seems useful and I'll probably end up using it sometime in the future, but I would have never known about it if it were not for this comment. Same as ctrl-L, and for 99% of people F5 and alt+left/right. There should be a page listed in the Firefox menu with a list of useful shortcuts, from most useful (F5, alt+left/right) at the top (so that normal people can get some efficiency gains easily) and going to to more obscure ones like shift+right click so that power users like us can... well, be power users.

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

#318

Post by dwb »

ko27 wrote: post #101
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…

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

That depends entirely on your interpretation of RFC 2119 in this context – whether you consider Google to have "valid reasons" or not. It's not an objective or inarguable issue.

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

#319

Post by mikorym »

dmethvin wrote: post #281
romaaeterna wrote: post #18

A few years ago, I left a $1000 tip at the restaurant up the street because Chrome filled out the tip field with my zip code (which thankfully merely defaulted to max $1000 instead). The tip field was off-screen, and the ordering software didn't have a confirmation screen, just a "we just charged your card $X amount" screen, which made my eyes boggle. EDIT: Looking at the original March 17th, 2015 bug, it would have…

This has a lot of really serious implications. I built a form for a charity that allowed users to buy a subscription but include an additional donation amount. Chrome was sometimes filling that field with the two-digit year. The charity got a lot of complaints and it ruined the trust relationship with the donors who didn't understand what was happening and thought it was intentional.

Chrome has other behaviour that I think violates a sort of trust relationship. One of which is that Youtube would ask you "do you want to install Chrome"? Almost as if your current browser is not "what you need to access Youtube". This is especially a problem for elderly people who often use the web but don't really understand how things fit together (the way 5 year olds actually do).
Post reply on HN