-
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
refactor: refactored InlineImageNode - spans for correct HTML #6214
refactor: refactored InlineImageNode - spans for correct HTML #6214
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
@@ -352,7 +352,7 @@ export default function InlineImageComponent({ | |||
return ( | |||
<Suspense fallback={null}> | |||
<> | |||
<div draggable={draggable}> | |||
<span draggable={draggable}> |
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.
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.
Thanks @potatowago. I'm actually the author of this plugin and thought I would tidy this up a little ;-)
Hi @58bits , sorry for the inconvenience caused in the CI do you mind merging latest Main to this branch before we try remerging this PR to main, to make sure all e2e tests are green. Thanks a lot! |
CI pass apart from flaky collab tests which will be addressed in #6238 |
[lexical-playground][inline-image-plugin] Refactor: Spans for correct HTML
Refactor
Description
Refactored InlineImageNode into its own directory, and changed inline image containing divs to spans for technically 'more correct' HTML for inline and float elements. Note that in theory there should be an 'inline' version of ContentEditable too.