Sorry about all the trouble you lot are having with this but, but I just tried (again) on my dev site and on the demo site and neither is displaying this behaviour when I follow these steps. It might depend on a specific configuration, or plugin you’re using, so perhaps you can share what you’ve customised from the default.
It could also be browser-specific, so that information could also help.
If we can’t reproduce it, I don’t know how we’re going to fix it so we’re going to need some more information to try to narrow it down.
The alternative text (when editing an image) showing a resource typeahead was fixed in 2.2.1