This is a common autocomplete/top-result UX mistake. If typing a substring of X autocompletes to X, then typing more of that substring of X, contiguously, must also autocomplete to X. This is a no-brainer (having the result change before you can stop yourself from hitting enter is easily one of the most frustrating things in all UX). However, it seems like people implementing clever auto-complete rules just don't care (I absolutely refuse to believe it's ignorance - it's impossible to be unaware of this problem if you're implementing autocomplete).

I assume the issue is poor decision making about rule conflicts. E.g., what's higher priority: Consistency, or exact-match? E.g. if "photo" auto-completes to "Photoshop", should "photos" auto-complete to "Photoshop" or "Photos"? I think it's "obvious" that consistency is more important here. If the user wants "Photos" despite opening "Photoshop" more often, let them configure the search explicitly to prioritize it, or allow them to select from a list of multiple matches.

And that's just a comparison against a single conflicting rule. Now imagine all the obscure rules they've implemented, for reasons varying from a misguided drive for "features" to nefariously pushing the user to click on what they want them to.