Re:“autocomplete=off is ignored on non-login input elements”
by Pxtl on Wednesday June 15, 2016 @04:19PM
(#11911867)
I've been trying to use the Facebook page on my phone since they've killed the FB Mobile web messenger and the amount the FB autocomplete and the Chrome autocomplete fight each other and mangle my text is spectacular.
Re:“autocomplete=off is ignored on non-login input elements”
by serge2k on Wednesday June 15, 2016 @04:29PM
(#11911935)
I'd much rather have things like that broken then have to futz around with someones stupid login form that disabled password pasting and autocomplete.
Re:“autocomplete=off is ignored on non-login input elements”
by tracker1 on Wednesday June 15, 2016 @05:22PM
(#11912242)
Man, is that annoying, or login forms that are in a dynamic dialog and/or ajax-login out of band instead of a post, so that it doesn't offer a save option... I mean, I tend to use LastPass over the built-in manager, just the same, it gets annoying when sites work extra hard to subvert those things that make actually using the web easier.
Along the same lines is one of the reasons I actually like OAuth/OpenID/OpenAuth logins, etc... simply that I can avoid yet another login that I only use on one site, with yet another password, that I generate and won't remember anyway.
Re:“autocomplete=off is ignored on non-login input elements”
by chrishacken on Wednesday June 15, 2016 @03:54PM
(#11911685)
" For example when the page has its own autocompleter"
Wouldn't that just override whatever values Chrome throws in there anyway? (If you're using JS.)
Re:“autocomplete=off is ignored on non-login input elements”
by draw_down on Wednesday June 15, 2016 @04:02PM
(#11911740)
No.
Re:“autocomplete=off is ignored on non-login input elements”
by jasonlotito on Wednesday June 15, 2016 @03:59PM
(#11911725)
There are ways to resolve those situations properly as explained in the link being discussed.
Re:“autocomplete=off is ignored on non-login input elements”
by draw_down on Wednesday June 15, 2016 @04:06PM
(#11911779)
So you defeat the autocomplete by messing with attributes in a slightly different way, and we've just gone in a circle. Great job everybody.
Re:“autocomplete=off is ignored on non-login input elements”
by mikeash on Wednesday June 15, 2016 @04:21PM
(#11911878)
That's pretty much the story of the web from day one, and I'm not sure if it can actually be avoided. The incentives and desires of the content producers, browser makers, and users are all too different.
A good example is the branch-switching widget on Github's repo page. Browser autocomplete is a major pain in the ass when trying to use this widget. The page can load all the branch names itself, but your dumbass browser is "helpfully" autocompleting a bunch of branch names that probably don't even exist anymore, or exist in other repos. Gee, thanks soooo much.