Put best autocomplete matches at bottom of list, not top

[gnprice]

That way they're in easy reach. In particular when using a phone with one's thumbs, the top of the screen can often be significantly harder to reach.

Because the query is at the bottom of the screen (in the compose box) and the list of autocomplete options opens upward from there, putting the best matches at the bottom is also logical because it puts them right next to the query (the one they're the best match for).

This applies to both ComposeAutocomplete (for autocompleting @-mentions, emoji, and so on from the content input) and TopicAutocomplete (for autocompleting topics from the topic input).

[apoorvapendse]

/assign

[apoorvapendse]

That way they're in easy reach. In particular when using a phone with one's thumbs, the top of the screen can often be significantly harder to reach.

I’d like to work on this @gnprice .
I’m thinking of returning a reversed list here and updating the relevant tests.

Does this approach work for you?

[gnprice]

Sure, assigned.

That sounds like a good start, but be sure to try the case where there are more results than fit at once, and the user has to scroll. (I.e. try that in your manual testing as you develop; and in tests you write as part of the PR; and in screenshots to illustrate your changes when you send the PR.) We'll want the best results to be visible, at the bottom of the list next to the input, and the long list of less-good results to be the ones that are out of view and have to be scrolled to get to.

[apoorvapendse]

Sure.

[apoorvapendse]

CZO