I genuinely can not even think how you mess this one up. highlighting a key being used is sign that click is registered correctly, and since highlighted key is what you expect, it seems the ui is supposed to pop that up. It also suggests that popping of keys happens independently of key input loop, and is likely that way for performance reasons. key entry should not wait for key pop up to finish, so they both must happen in parallel.

Now I guess the reason is maybe something like - hardcoding where a key would be in the display (or keyboard window coordinate) and if you register a click there, enter that key. Now that is roughly how a keyboard would work, but maybe they increased the hit target (you do not press at defined pixels on screen which lie exactly on middle of keys, so all keys have some “nearby fall zone” where if you click, the key is still registered. Now this should not happen normally, as pressing u should result in u, even if j’s fall zone is large enough to get to it (it should not be, at least not until you do something like swipe input and some prediction which sees what is more likely for the given coordinate and previous letters). Maybe some where the calculation for zones is borked. and it’s internal keyboard coordinate is not matching the keyboard.

Not saying errors in programs can not happen, but keyboard input seems one of things I assumed that you do once, and never touch again, as it is not really changing.

I’ve noticed a drop in accuracy as well. I’ve actually started using the finger-drag method to type since it seems to be more accurate.