feat: load Lexical Reader in SSR with a fake DOM#2979
Draft
Soxasora wants to merge 1 commit into
Draft
Conversation
…tationObserver, DOMParser and computed styles
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Server-renders the Lexical Reader by briefly giving Lexical a fake DOM.
initialContentEditableSSRtemporarily creates a fakedocumentviawithDOM(linkedom), then attaches it as Lexical's root element, allowing Lexical to render itsEditorStateinto a valid root. The resulting HTML is used as the content editable (what gets rendered) for Lexical during SSR.Screenshots
Lexical loads instantly
lexical_reader_SSR2.mp4
Additional Context
Should we remove HTML support at this point? We don't have another use for it and it's just wasted bandwidth.
I can see it being really useful for exports or no-js environments (
htmlparam) but nothing we currently support.Checklist
Are your changes backward compatible? Please answer below:
Yes, HTML is intact and still accessible via
htmlparamOn a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
6, in QA
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
Yes, still light QA in background
Did you use AI for this? If so, how much did it assist you?
No, although I got the idea from an example made by Claude online.