HTML tags are automatically removed from user name but error in workspace name

[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. Try setting a new user display name with html tag like
2. Notice that the is tag removed in name
3. Try changing the workspace name to
4. Notice the error that html tags are not allowed

Expected Result

While setting the name, the user should be alerted that tags are not allowed just like it happens in workspace

Actual Result

There is no error, the tags just get removed silently

Workaround:

unknown

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.2.72-0
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:

Screen.Recording.2023-02-16.at.1.55.19.AM.mov

Recording.1536.mp4

Expensify/Expensify Issue URL:
Issue reported by: @esh-g
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1676493009198069

View all open jobs on GitHub

[MelvinBot]

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

[MelvinBot]

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

[marcaaron]

I think it's expected based on... #13978

And also already planned here to update other places #14610

Not convinced we should prioritize this or handle it differently. Anyone entering HTML here is basically a hacker trying to do an xss attack. cc @ctkochan22 does that sound right to you? I think we can close this one out.

[ctkochan22]

Yeah, it's known and will be handled here: #14610

[laurenreidexpensify]

Cool am closing. also agree with @marcaaron that this is not our mainstream user behaviour.