6 ms·
Sometimes it's better to turn off for usability reasons, and the browser doesn't have a clue about when that's the case. For example when the page has its own a
by draw_down 10y ago
Sometimes it's better to turn off for usability reasons, and the browser doesn't have a clue about when that's the case. For example when the page has its own autocompleter, which has more information available to it than the browser does.
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.
- chrishacken 10y ago" 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.)
- draw_down 10y agoNo.
- jasonlotito 10y agoThere are ways to resolve those situations properly as explained in the link being discussed.
- draw_down 10y agoSo you defeat the autocomplete by messing with attributes in a slightly different way, and we've just gone in a circle. Great job everybody.
- mikeash 10y agoThat'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.
- Pxtl 10y agoI'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.
- serge2k 10y agoI'd much rather have things like that broken then have to futz around with someones stupid login form that disabled password pasting and autocomplete.
- tracker1 10y agoMan, 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.