tab completion treats search for @r to include users starting m

[michaelkaye]

Description

Typing @r<tab> in a channel does not tab complete to users with "r" at the start of their name.

I'm fairly sure this used to just show users which matched 'r'

Steps to reproduce

Type @r<tab> in the message box:

Get these options:

Describe how what happens differs from what you expected.

I would expect that matmaul no 'R' in display name or mxid, matthew and manu (an R in their mxID only: 'matrRix.org') are not offered as suggestions, and instead richvdh with R at the start of their name, to be among the first in the suggestions.

Beyond these first few users which are definitely wrong, the remaining users all start R or M as well - it's like the two letters are confused with each other.

Logs being sent: yes

Version information

• Platform: web

For the web app:

• Browser: Firefox 85.0.1
• OS: ubuntu
• URL: app.element.io

[michaelkaye]

This is persistent across switching away from the room and back

[michaelkaye]

This is present across all rooms i'm part of, and having tested all the lowercase letters of the alphabet, the only oddness is that "r" includes "m".

M does not include R though.

[t3chguy]

This is a side effect of allowing rn to match m by use of unhomoglyph https://github.com/nodeca/unhomoglyph

[michaelkaye]

No objection to "m" being shown iff there's no r's to go first; but exact matches should always take precedence over fuzzy matches.