-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Introduce HTML string document import #5895
Merged
Merged
Conversation
This file contains 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
This was referenced Aug 7, 2024
This was referenced Sep 20, 2024
This was referenced Oct 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new feature that allows importing the HTML string as documents.
More details about the current problem and the implemented solution.
Problem
Currently, the editor imports only the content inside the body, so if you try to import this content inside the main wrapper...
... and try to get its HTML content (eg. via
editor.getHtml()
), this is what you getAll the HTML document information is lost (eg. doctype, head, etc.), and some elements (eg. inside the
head
) are moved inside the body.This was intentional as the editor's main purpose was always to manage only the content of the pages but this is not always suitable for all use cases.
Solution
To support the document import, the HTML parser and the wrapper component were extended to handle those data.
In order to avoid possible breaking changes, a new option
asDocument
is required.Now the document information will be preserved if you try to get its HTML.
Additional API
The HTML document data are stored inside the wrapper component.
Caveats
asDocument
option is only valid if used on the wrapper component.config.canvas.styles
/config.canvas.scripts
options, those will be replaced with the content of the imported document.