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

Chrome does not respect autocomplete=off (2018)

bugs.chromium.org

Post reply on HN
Print view View original

61–70 of 84 posts

Re: Chrome does not respect autocomplete=off (2018)

#61

Post by mantap »

Spivak wrote: post #16
nikanj wrote: post #2

It’s pretty incredible to see the amount of steaming developers commenting on this issue. What tools do developers have, when platform providers turn a deaf ear to their needs?

The problem is that you’re only seeing angry developers and not the angry users frustrated that they can’t use autofill on sites that disable it for no real reason. Sites being able to change the behavior of the user-agent is almost always a bad thing. autocomplete=off should just be removed and it be entirely up to the user-agent whether it gets used like reader mode.

You've got to consider the 2nd order effects. Remove autocomplete=off? Developers will be forced to make their own DIY crappy text inputs just to get rid of it. And break everything but English input in the process.

Re: Chrome does not respect autocomplete=off (2018)

#62

Post by crznp »

Spivak wrote: post #16
nikanj wrote: post #2

It’s pretty incredible to see the amount of steaming developers commenting on this issue. What tools do developers have, when platform providers turn a deaf ear to their needs?

The problem is that you’re only seeing angry developers and not the angry users frustrated that they can’t use autofill on sites that disable it for no real reason. Sites being able to change the behavior of the user-agent is almost always a bad thing. autocomplete=off should just be removed and it be entirely up to the user-agent whether it gets used like reader mode.

Alternately: User-agents changing the behavior of well-written sites without user knowledge is almost always a bad thing.

Giving the user more control is great: things like reader mode, option to disable auto-play video or options to kill resource-intensive scripts. This isn't a tool for the user, it is the browser's behavior whether the user wants it or not.

If autocomplete=off is user-hostile, then it should be changed in the spec. The spec gives a few use cases (site has its own autocomplete, field is sensitive information that shouldn't be cached, field is a one-time key). If autocomplete=off is removed, how would those cases be handled?

https://html.spec.whatwg.org/multipage/form-control-infrastr...

Re: Chrome does not respect autocomplete=off (2018)

#63

Post by pwdisswordfish0 »

meibo wrote: post #40
kelnos wrote: post #33

Earlier quoted context omitted.

I don't think that's material. If we're talking about corporate policy on corporate-owned machines, employees shouldn't be complaining to IT that their favorite websites aren't working properly in Firefox. If they do, the canned IT response should always be "why are you doing personal tasks on your work machine?" As long as the corporate/enterprise apps work on Firefox (which they should?), it's not a problem for a c…

Companies also want their employees to be as productive as possible, which are likely already using Chrome at home because it has the best usability and quality of life for non-technical users. I don't think any IT department worth their while would ban worthwhile software because of some agenda that frankly just doesn't matter too much to most regular users, at least in an US context. In the EU this might be a bit d…

> Companies also want their employees to be as productive as possible[...] I don't think any IT department worth their while would ban worthwhile software

This shows a disconnect / bubble. Lots of IT departments require permission to install any software, i.e., a whitelist, rather than the blacklist being proposed (and which is fine in this instance). Granted, many of those places don't care about their employees being as productive as possible (even if they tell themselves they do), and their IT departments aren't worth their salt, and this tends to be norm, unfortunately.

Re: Chrome does not respect autocomplete=off (2018)

#64

Post by city41 »

Spivak wrote: post #13
colejohnson66 wrote: post #10

Earlier quoted context omitted.

I hate password forms that do this

I wish I didn’t have to disable clipboard events because of sites that think they know better to disable paste.

Curious how you disable clipboard events? I always go into the dev console and do $0.value = ''

Re: Chrome does not respect autocomplete=off (2018)

#65

Post by tshaddox »

booblik wrote: post #15

Cool. Do paste blockers next.

It's pretty easy to make a website that has things that look and act like text inputs but which cannot be pasted into and cannot be detected as text inputs by the browser (short of something like computer vision, which I doubt will work well in practice).

Re: Chrome does not respect autocomplete=off (2018)

#66

Post by shepherdjerred »

tshaddox wrote: post #65
booblik wrote: post #15

Cool. Do paste blockers next.

It's pretty easy to make a website that has things that look and act like text inputs but which cannot be pasted into and cannot be detected as text inputs by the browser (short of something like computer vision, which I doubt will work well in practice).

Don't give them any ideas

Re: Chrome does not respect autocomplete=off (2018)

#67

Post by dmitrygr »

rurp wrote: post #54
dmitrygr wrote: post #22

GOOD! Acting like a user agent, as it should be! If only there was also a way to cause unending pain to anyone who created those nasty "do not paste in here" javascript tricks too..

That's great that Chrome happens to work as you like, but I am also a user and hate this behavior. How do I get Chrome to function as a user agent in this regard?

https://www.computerhope.com/issues/ch001377.htm#chrome

Re: Chrome does not respect autocomplete=off (2018)

#70

Post by maple3142 »

aftbit wrote: post #68

Why do forms still have nopaste support then? My bank occasionally makes me type an account number that I've copy/pasted from elsewhere in its interface. :(

It is not just a simple nopaste support, but a paste event listener. I guess back websites just uses preventDefault to prevent pasting. Although this is anti user, but it also has good use cases such as pasting image into a rich editor. Websites like Google Doc do have legitimate use of this feature.
Post reply on HN