Alpha autocomplete vs closest match to what I am actually typing is super annoying!

Hi Andy - thanks for taking the time to share this feedback! I’ve passed along to our Product team. 

hi @andy, thank you for this feedback. It’s the first time i’m hearing about this, but you’ve made your point quite clear. I can see how this current behavior is not particularly helpful.

You focused your screenshots on Tags in the Upload-screen, yet there’s also a metaproperty-type autocomplete which is actually hindered from the same behavior.

I would rather it list those options last that match the word but don’t start like how I typed

Would you envision a solution as in this quick & dirty mockup below?

Thinking about it a little longer, there could be 3 layers for showing the text matching the input:

When typing Tree:

1/ show exact match  (Tree)

2/ show partial matches (Palm Tree)

3/ show close matches (Street, Street Art)

Thanks @Klaas de Bont that would be super helpful, the way I imagine it would be like this:

As I type “Tree” it would autocomplete to the closest match to what I am typing so it might look like this:

Typed: Tre

Results would be alpha close to what I am typing preference to how I start it, so it must start with Tre to show up first:

Treat

Tree

Trend

Then close matches

Once I type the second “e” to make it “Tree” it would change to:

Tree

then close matches as you have above

Does that make sense?