Mark down - Different colour of strikethrough on email depending on bold mark down position

[lanitochka17]

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

---

Version Number: 1.4.58-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR around #38152

Action Performed:

1. Go to staging.new.expensify.com
2. Go to any chat.
3. Type the following text with mark down (with no space):

• ~ hello.com ~ *
  ~ * hello.com * ~

Expected Result:

The color of strikethrough in the preview should be consistent

Actual Result:

The color of strikethrough in the preview is different depending on the position of bold mark down.
When the mark down is in this order * ~ hello.com ~ *, the strikethrough is blue
When the mark down is in this order ~ * hello.com * ~, the strikethrough is white

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6431683_1711724092674.20240329_225011.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[lanitochka17]

@flodnv FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #vip-vsp

[thienlnam]

Not a deploy blocker - added to the main tracking issue

[thienlnam]

This is pretty low on the priority list of other live markdown issues, so going to put this on a monthly

[thienlnam]

Closing, looking at this again I'm not sure there is really a problem here