[HOLD for payment 2023-03-06] [$1000] Inconsistent formatting on multi-line text

[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. Open staging.new.expensify.com
2. Open a chat and send this :

*this is
bold text*

4. Open a chat and send this :

 _this is
 italic text_

Expected Result:

The italic text (second chat) should be italicized

Actual Result:

The italic text isn't italicized

Workaround:

unknown

Platforms:

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

• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.62-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:

Recording.1407.mp4

Expensify/Expensify Issue URL:
Issue reported by: @kerupuksambel
Slack conversation: (https://expensify.slack.com/archives/C049HHMV9SM/p1675081190765919)

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014df7aa17e60e5f61
• Upwork Job ID: 1623064663503052800
• Last Price Increase: 2023-02-07

[greg-schroeder]

Bug0 Triage Checklist

Note: see this SO for more information.

• The "bug" is actually a bug
• The bug is not a duplicate report of an existing GH.
  • If it is, close the GH and add any novel details to the original GH instead
• The bug is reproducible, following the reproduction steps.
  • If the GH doesn’t have steps to reliably reproduce the bug and you figure it out, then please add them.
  • If you’re unable to reproduce the bug, add the Needs reproduction label.
  • Comment on the issue outlining the steps you took to try to reproduce the bug, your results and tag the issue reporter and the Applause QA member who created the issue. Ask them to clarify reproduction steps and/or to check the reproduction steps again. Close issue.
• The GH template is filled out as fully as possible
  • The GH body and title are clear (ie. could an external contributor understand it and work on it?)
• The GH was created by an Expensify employee or a QA tester
• If the bug is an OldDot issue, you should decide whether it is widespread enough to justify fixing or it is better to wait for reunification. If it’s better to wait, close the GH & provide this justification
• If there's a link to Slack, check the discussion to see if we decided not to fix it
• Decide if the GH should be resolved by an External contributor or Internal engineer, add the appropriate label

[greg-schroeder]

I can reproduce this on Staging and on Prod

[greg-schroeder]

This looks like a regression of #13727

cc @neil-marcellini @michaelhaxhiu

[neil-marcellini]

I'm a bit swamped right now catching up from OOO, but I'd be happy to CME on this one and have a contributor identify the root problem / regression for us.

[MelvinBot]

@greg-schroeder Still overdue 6 days?! Let's take care of this!