Skip to content

DOC-3147: DomParser no longer tries to fix some nodes when parsed with a context and Improved structure retention when inserting invalid HTML fragments #3779

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.

Sign up for GitHub

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

Merged
kemister85 merged 2 commits into from
Jul 15, 2025
Merged

DOC-3147: DomParser no longer tries to fix some nodes when parsed with a context and Improved structure retention when inserting invalid HTML fragments #3779

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f36e7a
DOC-3147: DomParser no longer tries to fix some nodes when parsed wit…
kemister85 Jun 30, 2025
fcb35a0
Merge branch 'feature/8.0.0/DOC-3147' into feature/8.0.0/DOC-3147_TIN…
kemister85 Jul 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions modules/ROOT/pages/8.0-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,6 +286,14 @@ This behavior is now enabled by default, but can be disabled by setting `pagebre

For more information on the `pagebreak_split_block` option, see xref:pagebreak.adoc#pagebreak_split_block[pagebreak_split_block].

=== DomParser no longer tries to fix some nodes when parsed with a context
// #TINY-8205

Previously, the `DomParser` would attempt to fix invalid HTML structures when parsing with a context, such as when inserting content into a specific element. This behavior lead to unexpected results, especially when the structure was not valid in the context of the parent element.

In {productname} {release-version}, the `DomParser` has been updated to no longer attempt to fix invalid nodes when parsing with a context. Instead, it will validate the nodes and only insert them if they are valid in the context of their parent element. If the nodes are invalid, they will not be inserted.


[[removed]]
== Removed

Expand Down Expand Up @@ -392,6 +400,13 @@ Previously, applying different font sizes to nested elements could result in inc

{productname} {release-version} introduces a fix that ensures line heights are calculated based on the font size visible in the new line, rather than inheriting line-height from parent element. This means that when different font sizes are applied within the same content, the line heights will be consistent and proportional to the visible font size.

=== Improved structure retention when inserting invalid HTML fragments
// #TINY-8205

Previously, when inserting HTML fragments through APIs or pasting, the parser would attempt to fix invalid structures, which could lead to the loss of valid structures like tables and lists. This behavior was inconsistent and could result in unexpected outcomes when handling complex HTML content.

In {productname} {release-version}, the parser has been updated to improve the retention of structures when inserting HTML fragments. It now validates these fragments in the context of their parent structure, ensuring that valid structures are preserved even if the fragment contains invalid HTML resulting in more predictable and desirable outcomes when handling complex HTML content.


[[security-fixes]]
== Security fixes
Expand Down