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

Post by kps » Sun, Oct 13, 2019, 4:33 PM UTC

Reelin wrote: post #95

Carpetsmoker wrote: post #72

Earlier quoted context omitted.

> 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 And here I was, all along, thinking that website authors were in control of how their websites behaved. How silly of me!

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…

Post by Osiris » Sun, Oct 13, 2019, 4:39 PM UTC

Rapzid wrote: post #251

michaelt wrote: post #211

Earlier quoted context omitted.

I've heard plenty of people on HN say password managers should ignore autocomplete=off and I agree with them. Because that setting is mostly applied by organisations like banks who incorrectly think they're making things more secure by doing so. IMHO there are cases where autocomplete=off should be respected, and other times when it shouldn't be - it's certainly not as simple as saying always do or always don't respe…

Well, all major browsers now ignore it on password fields so the browser ship has sailed on that one: > This is the behavior in Firefox (since version 38), Google Chrome (since 34), and Internet Explorer (since version 11). - MDN

Post by phendrenad2 » Sun, Oct 13, 2019, 4:47 PM UTC

Post by pjmlp » Sun, Oct 13, 2019, 4:52 PM UTC

The_rationalist wrote: post #262

rndgermandude wrote: post #204

Earlier quoted context omitted.

>I can tell you that the higher management at Google does not dictate chromium changes as they are too technical for them. Tell that to the webRequest API that ablockers use. >As you said for the exceptions, Microsoft can maintain a fork, it's still order of magnitude more economic and smart than to constantly duplicate work in a redundant browser (firefox) Chrome is the redundant browser. Firefox was here first.

webRequest API Well maybe it's an exception, but they have technical reasons mostly. Webrequest v3 is not stable so wait and see. Chrome is the redundant browser. Firefox was here first. Well Chrome is based on khtml which is not that new but yeah Netscape navigator precede it. Indeed it would have been better if chrome was based on gecko (FF) at the time. But now Firefox can be thought of the redundant browser becau…

Post by pjmlp » Sun, Oct 13, 2019, 4:53 PM UTC

IshKebab wrote: post #274

pjmlp wrote: post #74

Earlier quoted context omitted.

Well, shortly you won't have a choice anymore. And there was a choice, back then alternatives like Opera, did actually ship their own engine.

We're not talking about choice for users . This is about choice for developers .