Chat - Header markdown has bigger font-size in compose box than in chat history

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.39-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: https://expensify.testrail.io/index.php?/tests/view/4292602
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Log in to New Expensify
2. Navigate to any chat
3. Draft message with header markdown
4. Verify header font size
5. Send message
6. Verify header font size in chat history

Expected Result:

Header font size should be equal in compose box and in chat history, or bigger in chat history as it is in Production

Actual Result:

Header has bigger font size in compose box (19px), than in chat history (17px)

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

Bug6373477_1707481778307.2024-02-08_20-48-02.mp4

View all open jobs on GitHub

[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.

[melvin-bot]

Triggered auto assignment to @neil-marcellini (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[lanitochka17]

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

[neil-marcellini]

This comes from a new feature, Live Markdown Preview for web. I think we should fix it, but I don't think it should block the deploy. I would rather have live mark down preview deployed now with this small bug, and then fixed later.

[melvin-bot]

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

[thienlnam]

Thanks, adding this to the tracking issue - but since we reverted the PR this no longer exists

[melvin-bot]

This issue has not been updated in over 15 days. @johncschuster, @thienlnam eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[tomekzaw]

Should be already fixed with #36319