Using a comma after mention doesn't display the blue highlight (but still recommendation is shown)

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to staging dot on web chrome
2. Go to any chat
3. Type in @ and select any user
4. Now try to add comma just after the mention name without any space and notice that the blue color highlight disappears but the recommendation is still shown
5. Try to follow the same step with other special characters like dot, slash,dollar, brackets , add, subtract etc sign and notice that the mention suggestion disappears

Expected Result:

Using a comma after mention should either hide the mention name in a similar way how adding other special characters does OR if a recommendation is shown then it should be highlighted in blue

Actual Result:

Using a comma after mention doesn't display the blue highlight (but still recommendation is shown). Whereas for other special characters, the recommendation goes away.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.16-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

error-2023-05-17_17.09.55.mp4

Recording.677.mp4

Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684323901466969

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[dukenv0307]

This issue should be handled in this PR by add , to SPECIAL_CHAR_OR_EMOJI regex and MENTION_REPLACER regex
cc @allroundexperts @sakluger @mananjadhav

[sonialiap]

Thanks @dukenv0307!

[sonialiap]

Resolved by #19004

Tested on staging

Screen.Recording.2023-05-25.at.11.39.22.PM.mov