-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HIGH: [Live Markdown] Tracking Live Markdown Issues #36071
Comments
Please assign me for visibility |
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. |
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. |
@tomekzaw, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Working on it |
@tomekzaw, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Working on it |
@tomekzaw, @thienlnam Huh... This is 4 days overdue. Who can take care of this? |
Working on it |
@thienlnam - shoudl we move #39275 to |
I think we can remove the blocker from that issue, seems like that just came out as well |
Oops, I had linked the wrong issue, I meant #39263, but that's been added to the deploy blocker section. Thanks! |
@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? |
Ah yeah definitely doesn't look like it needs to block deploy, I've added it above as part of MED |
Hi, I found an issue with the live markdown on the web. The I can reproduce it with this minimal code: 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. |
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. |
Adding this issue as well - Chat- Nested quotes disappear when editing if different levels of quotes are present |
One more to add: |
We're still chugging along - almost done with all critical and highs |
SWM is OOO this week, we're still chugging through |
Just cleaned up the tracking issue, the list is dwindling! |
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 |
Tracking issue for all Live Markdown bugs
CRITICAL
HIGH
MED
LOW
The text was updated successfully, but these errors were encountered: