The autofill popup definitely has some bugs especially on mobile and with so many more emotes all with their own tags in the system. Buuuuut, at least on desktop, typing :cringe is showing me things with exact title or tag matches first (the first 7 results) and then it descends into gibberish partial word/letter combo matches, which is annoying but I think expected?

If there is an issue, from what I’ve seen, its weird rendering on mobile, and possibly not starting scrolled to the top of the list, landing people in the middle of the gibberish results to start with instead. Does that line up with what you’re seeing?

If anyone wants to look into it, we are using this library: https://github.com/zurb/tribute Calling it here: https://github.com/hexbear-collective/lemmy-ui/blob/1787a778f8cf01fb1b00262e44ae8e49f9b3ccc1/src/shared/markdown.ts#L335

Looks like we aren’t setting a maximum for how many items it should load. I think it would be reasonable to do that.

Yeah i noticed that when i implemented it; The js library for the inline emojis has a search functionality, and it basically finds all emojis with name/keywords that contains the letters that you are searching for, and ranks them as most matching to least. So searching ‘cringe’ will search for all emojis that have the letters ‘c’ ‘r’ ‘i’ …, with the top ranked emojis having the most letters and in typed order.

I tried to work around it a bit but the library doesn’t have any hooks for it as far as i saw.

Oh! One thing I didn’t mention that I would be remiss not to: Use the emoji mart by clicking on the little smiley face at the top of the text entry box. It has better search, but displays the emotes very tiny. Totally separate system from the autocomplete popup deal I discuss in my other comment

deleted by creator

I’ve always gotten very little - cough - feedback when I’ve posted in c/feedback. I guess c/hexbear is always where the party is.