HIGH: [Live Markdown] Tracking Live Markdown Issues

[thienlnam]

Tracking issue for all Live Markdown bugs

CRITICAL

• [HOLD for payment 2024-05-08] Web - Chat - Composer jumps when entering first emoji #39267

HIGH

• [HOLD https://github.com/Expensify/react-native-live-markdown/pull/394][Live Markdown] Support inline code background style #39518

MED

• [HOLD PR #39343][$250] Thread-Cursor is hand cursor instead of text cursor when hovering over edit composer in thread #39301
• [Live Markdown Issues] Android - Chat - App isn't responding on pasting email repeatedly in compose box #36354
• [$250] Chat - Text in compose box blends with background when theme was changed in device settings #39348

LOW

• Mark down - Different colour of strikethrough on email depending on bold mark down position #39266
• [$250] Code blocks of only spaces don't render #31633

[tomekzaw]

Please assign me for visibility

[tgolen]

I'm bumping up the priority of this since several of the reported bugs are deploy blockers. I recommend reverting the LiveMarkdown PR, fixing the bugs that have been reported, and then trying again.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

@tomekzaw, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!

[tomekzaw]

Working on it

[melvin-bot]

@tomekzaw, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!

[tomekzaw]

Working on it

[melvin-bot]

@tomekzaw, @thienlnam Huh... This is 4 days overdue. Who can take care of this?

[tomekzaw]

Working on it

[tylerkaraszewski]

@thienlnam - shoudl we move #39275 to BLOCKING DEPLOY or should we remove the deploy blocker from that issue?

[thienlnam]

I think we can remove the blocker from that issue, seems like that just came out as well

[tylerkaraszewski]

Oops, I had linked the wrong issue, I meant #39263, but that's been added to the deploy blocker section. Thanks!

[tylerkaraszewski]

@thienlnam I got tagged for another deploy blocker that might be related: #39301

I don't know if this is severe enough to be a deploy blocker. Thoughts?

[thienlnam]

Ah yeah definitely doesn't look like it needs to block deploy, I've added it above as part of MED

[bernhardoj]

Hi, I found an issue with the live markdown on the web. The autoFocus prop of the composer seems not working. I tried setting it to false but the composer is still auto-focused.

I can reproduce it with this minimal code:
<RNMarkdownTextInput autoFocus={false} selection={{start: 0, end: 0}}/>

If there is a selection prop, the input will always be auto-focused. If I remove this live markdown source code, then the issue is gone.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[slafortune]

Adding this issue as well - Chat- Nested quotes disappear when editing if different levels of quotes are present

[twisterdotcom]

One more to add:

• [$250] Code blocks of only spaces don't render #31633

[thienlnam]

We're still chugging along - almost done with all critical and highs

[thienlnam]

SWM is OOO this week, we're still chugging through

[thienlnam]

Just cleaned up the tracking issue, the list is dwindling!

[thienlnam]

Closing this! We've worked through all the critical issues, I think every issue from here on out can just be addressed independently. We're still working through #39518 but there's no longer a need for this main tracking issue