That kind of shit is frustratingly common these days. I sometimes use the search box in the Twitter app to navigate to one of the profiles I follow. So I tap on the magnifying glass, enter the first few letters of the account name, see the account in the search results (immediately, because it has my list of followed accounts cached locally, I guess), and I tap on that account ^W^W the completely irrelevant search result that appeared a fraction of a second before my finger touched the glass.

I've never understood this. You shouldn't be able to activate a control that appeared, or whose meaning changed, an amount of time ago that's smaller than human reaction time (0.2 sec or whatever).

Okay, now try typing on a smartphone keyboard that animates an enlarged bubble for every key the user taps.

The user thinks 'type, "hello"' and the muscle memory flits between 'h', 'e', 'l', 'l', 'o' with way less space between each letter than the user's reaction time. If they mistype a letter and want to correct it, they'll probably continue for one or two strokes and either navigate back or tap backspace several times.

I had "except in cases where the user can plausibly predict the change" originally in my comment before deleting it for being verbose. Yes, of course this UI guideline is not a hardware rule. (Also, in the case of typing it's actually not an issue. The visual of the button is revealed but yo could never click the bubbles so the functionality of the button didn't change. A better example is a moving target in a video game.)

Always goes to Edge for me too despite the fact that I've set chrome as my default. Why do I need a web search in my windows bar anyway? Does anyone use this workflow?