when you click on @qwe_rfv, It will work normally
But when you click on @QwE_rFv… did you get it?
AI-generated summary
Users reported a bug where clicking a mention like @QwE_rFv opens a user card displaying the username exactly as typed, preserving incorrect capitalization, rather than normalizing it to the canonical form (e.g., @qwe_rfv). Don linked to a related meta discussion, noting that user cards currently reflect the case of the mention, not the stored username. qwe_rfv questioned whether preserving incorrect casing (e.g., @Do n) is desirable, suggesting automatic normalization. michaeld humorously noted that users like BenDover might prefer their chosen casing. Moin proposed always displaying the canonical form, but awslabspl and michaeld clarified that Discourse usernames are case-aware but not case-sensitive — meaning USER, user, and UsEr refer to the same account. sam labeled the issue pr-welcome, suggesting it’s minor but fixable by adjusting the user card to display the canonical username after loading. shauna submitted a PR to fix it, and zogstrip thanked both the reporter and fixer. The fix ensures mentions like @sAm display as sam in the user card, improving consistency.
1 Like
It works with both mentions for me.
2 Likes
I think this is related Missing capitalisation in username on usercard opened from message participants
On user card the username is case sensitive. I think it push the mentioned username to the user card.
4 Likes
Yes, That’s right. But Isn’t @Don really ummm… kind of bad?
I think It got to be like this: when someone mention @QwE_rFv , automatically turn Into @qwe_rfv
1 Like
I don’t think that the user called BenDover would agree with you 
3 Likes
Why not always match the username? So beNdOVeR would become BenDover.
2 Likes
@Moin
Because these are two different usernames maybe?
No, usernames on Discourse are case aware but not case sensitive. USER, user and UsEr Are the same user.
2 Likes
I am putting pr-welcome on this.
When you click @sAm you should probably see sam in the user card … not sAm
It is very minor, has very little user impact, probably an easy fix to correct it after the card loads all the data from the server.
5 Likes
I opened a PR for this:
https://github.com/discourse/discourse/pull/16539
8 Likes
