4 ms·
> chrome autofilling to an old address I completely disable autofill in the first place. As an added bonus, sites can't have hidden fields that get autofilled
by inetknght 9y ago
> chrome autofilling to an old address
I completely disable autofill in the first place. As an added bonus, sites can't have hidden fields that get autofilled with my information either.
Second, I'd strongly argue it's your fault for not looking at what Chrome filled into the fields.
> if you think that you are doing someone a favor by doing work ahead of time please stop.
To be fair, they probably are doing some people a favor. I just think that things should be opt-in instead of opt-out though.
If things don't get opted into, then perhaps you should look to see why. Maybe people just don't know about it. Time to create some quick tutorials then.
- pg_bot 9y agoIt is often the case that I type faster than the UI can respond. So if I am tabbing through form fields and the last one changes everything above the viewport without me noticing it's an easy mistake to make. I usually won't double check shipping addresses because I typed the correct thing in the first time. At the end of the day it is on me to catch these kinds of things but I am sure you can understand my frustration.
- inetknght 9y agoThe only UI that is too slow to respond on modern hardware is a UI which is so laden with shitware. There's absolutely no other reason for a UI to be too slow to respond to typing; whether it's a terminal application, a native application, or a browser GUI. A GUI that changes what you've typed into some field (especially when you're not looking) is a prime example of UI dark patterns and shitware.