-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[lexical][lexical-devtools-core][lexical-playground] Bug Fix: fix TextNode importDom highlight formatting #6518
Conversation
Pull request facebook#3583 by @moy2010 added a new textformat (which is helpful), but if we use HTML to serialize it gets lost because importDOM is not parsing the mark. - Added the missing mark entry - Added a highlight formatting menu entry to playground for manual testing (including icon, and CSS theme) - added the missing entry in devtools to show format: highlight - added a test to check for mark on html past
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks good but the conflicts need to be resolved before this can be merged
@etrepum I've created a new PR #7186 that resolves these merge conflicts. The new PR:
Feel free to review the changes in the new PR. Once approved, we can close this PR in favor of #7186. |
Description
Pull request #3583 by @moy2010 added a new textformat (which is helpful), but if we use HTML to serialize it gets lost because importDOM is not parsing the mark or if we past HTML with
<mark>
, but the editor is already capable to export<mark>
and set IS_HIGHLIGHT.Closes #6498
Test plan
After