fix (tiptap): don't render html files via html strategy#2774
Merged
Conversation
2b5b931 to
2ee3349
Compare
This was referenced Jun 30, 2026
Member
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
kulmann
added a commit
that referenced
this pull request
Jun 30, 2026
[stable-7.1] fix (tiptap): don't render html files via html strategy (#2774)
AlexAndBear
added a commit
that referenced
this pull request
Jun 30, 2026
Cassolette
pushed a commit
to Cassolette/opencloud-web
that referenced
this pull request
Jul 1, 2026
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
2 participants
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.
Summary
This PR changes how HTML content is handled inside Tiptap.
Reason for this change
Previously, HTML content was rendered directly inside the editor. However, we discovered that Tiptap automatically strips certain HTML structures, such as
<div>elements, during parsing.This can lead to unintended data loss, since valid HTML content may be modified or removed when processed by the editor.
What changed
Why this is better
By no longer rendering raw HTML inside Tiptap, we prevent the editor from silently altering unsupported HTML structures and reduce the risk of accidental data loss.
Related Issue
<body>#2773How Has This Been Tested?
Types of changes