4 ms·
> I can't offer a general solution, but if password managers simply refused to autofill to any field other than the one with the matching standard autocomplete
by Griffinsauce 6y ago
> I can't offer a general solution, but if password managers simply refused to autofill to any field other than the one with the matching standard autocomplete attribute, web developers might start doing the right thing.
Unlikely. The password managers would just lose users.
I've even caught myself being annoyed at 1Password when it doesn't work while the cause is obviously the website doing some stupid thing.
I wonder how 1Password works on this problem though, do they just accept the crap and keep working on their guessing magic or do they also invest in standardization?
- chrisandchris 6y agoI always find it very interesting how the 1Password X (the standalone extension) team seems to work half the day just to fix some random website. At least their „fixed“ section of the release notes consists usually of a listing of websites where autofill does (did) not work [1]. [1] https://app-updates.agilebits.com/product_history/B5X https://app-updates.agilebits.com/product_history/B5X
- wwn_se 6y agoSome password manager allow you to config those parameters yourself but I guess that would not work in this case. Hopefully hardware tokens can help us get rid of passwords soon.
- diminutivesloop 6y agoOne solution could be to very prominently highlight auto-filled fields especially if the standard auto-fill attributes are missing. That might at least help some users avoid submitting info they didn't intend to.