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.
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.
And you think that is the right call for the majority of people?
Also, in addition to auto correcting words, your phone also auto corrects individual key presses based on the word you are typing. The same physical impact on your screen will register a different letter based on the letters that come before it.
So part of your “typing on glass accuracy” is dependent on a designer designing that feature that “does work ahead of time”.
No. Certainly not on a desktop, where I type much faster than any suggestion can appear (esp. infuriating on IDEs); usually not on a phone either, where "corrections", while sometimes faster than me, are always wrong.
But changing a word for another makes a sentence unintelligible and blocks or at least seriously slows down communication.
It's reasonably fast, I don't have to aim for tiny boxes with my fat fingers and it takes care of accents when I type in french. The correction algorithm is also getting better (albeit still far from perfect); sometimes it'll correct the previous word based on what I enter next. If you want me to disable this you'll have to give me a full size keyboard as a replacement.
It seems to me, speed is only an issue for long texts, and why would people type long texts (or lots of small ones) on a phone? Can't that wait until they're in front of a proper computer?
> If you want me to disable this
I don't want you, or anyone, to do anything ;-)
I simply find it strange that people rely on autocorrect, and then send a second message immediately afterwards, to say correctly what autocorrect got wrong. It seems it would be faster, and better, to get it right the first time than the current sequence of "type, send, proofread, retype, resend".
Survivorship bias: You cannot see the (usually much larger) number of words that were correctly autocorrected.
Auto-correct mishaps happen (especially when using multiple languages at the same time) but are fairly rare. It's a trade-off, it makes the majority of my typing much quicker and accurate, but I have to be careful about a few things.
Edit: as a non-native speaker, I don't really make spelling mistakes in English, either I know a word or I don't, so that's not a reason for me to use auto-correct.
…On the other hand, my teenage younger sister has always used her phone with autocorrect disabled (just because she doesn't like the capitalization), and she types pretty quickly. Maybe it's just a matter of training yourself with autocorrect off, and eventually you can type accurately while keeping the same speed. But I'm not sure. There's no doubt that training would help, but can it make up the full difference, compared to a user well-trained with autocorrect on? (…And for that matter, if I care about speed so much, shouldn't I switch to a swipe-style keyboard? But that's a separate discussion.)
Anyway, the fundamental problem is that without the tactile feedback of a physical keyboard, it's much easier for your fingers to get misaligned, so the relative positions of the taps might be reasonably correct but the absolute positions are totally messed up. Even though you can see when you make a typo, humans have pretty high latency in responding to visual feedback, and you only get the feedback after the fact (whereas on a physical keyboard you can feel if you're in the wrong place before you've actually pressed down on the key). It seems more efficient to just type the whole word at once, and even if you were misaligned, most of the time autocorrect will figure out what you meant. (Especially if you keep going with the sentence, which can change previous words after they were seemingly finalized. I used to go one word at a time, stopping to correct any word that turned out wrong, but after I learned to trust autocorrect a bit more I realized that some of those corrections were unnecessary. This applies especially to the word "its", which autocorrect likes to change to "it's" but will often change back when appropriate.)
Actually, I make typos on physical keyboards too - which I'd like to think is just a side effect of being a fast typist, though I'm probably less accurate than most - but my impression is that those are more often timing rather than positioning related, and I can often tell they've happened by feel alone, letting me hit option-delete to redo the word immediately without waiting for visual feedback to go through my head...
Would be nice to be able to have an escape word and spell the previous word by letters. Or get out into some control sequence :)
Maybe there should be an app for that!
chrome://settings/autofill
Can see validity in your other points, but I don't think this is always true. For example, I find it useful when looking up classical musicians on youtube to see what works they are most famous for playing
On the other hand, assuming know what the user "really" wants to do and doing that work ahead of time without asking first is arrogant and frustrating. If this also breaks existing behavior, it's also teaching people to treat your software as unreliable, possibly hostile, unpredictable toy they they should avoid when possible.
Tools need to be reliable, and that includes reliably following the user's orders.
I've had problems like chrome autofilling to an old address so a package gets delivered to the wrong location, or having to constantly edit text messages back to what I originally wrote because the program decided I was wrong.
When designing anything, if you think that you are doing someone a favor by doing work ahead of time please stop.