Chat - Composer flickers when using header markdown

[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

Action Performed:

1. Open a chat
2. Start typing # followed by any letter (Preferebly upper case letter)

Expected Result:

Composer should not flicker

Actual Result:

Composer flickers for a second while typing the letter followed by #

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

Bug6431621_1711720400855.38152.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @pecanoro (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]

@pecanoro 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

[thienlnam]

Not a blocker, added to the main tracking issue

[pecanoro]

@thienlnam Even if not a deploy blocker, who is fixing this anyhow? And why unassigning me?

[thienlnam]

SWM is fixing these in order of priority of the tracking issue - I unassigned since this came from the live-markdown PR we just merged and since this is lower on the priority list it might be a while until we get to this

[pecanoro]

@thienlnam Ahh got it! I don't mind reviewing the PR so I get to learn how this works, so I would love to stay assigned!

[pecanoro]

Still no update, agency is working on higher priority issues for markdown

[pecanoro]

Still no update, agency is working on higher priority issues for markdown

[pecanoro]

Still no update, agency is working on higher priority issues for markdown

[thienlnam]

@BartoszGrajdek Do you think you could add this one to your list?

[BartoszGrajdek]

I believe @Skalakid was working on this 👀

[BartoszGrajdek]

But I can't reproduce it anymore, are you sure this bug is still happening? @thienlnam

[thienlnam]

Ah yeah I can't reproduce either, this was probably fixed in one of our version bumps - @pecanoro feel free to close if you are also unable to reproduce

[pecanoro]

Same, closing!

[Skalakid]

I fixed that in #40128 in similar issue, so the problem is gone :D