Skip to content

DOC-3223: Encoding provided in the charset meta attribute would not be detected #3882

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 3 commits into from
Oct 19, 2025
Merged

DOC-3223: Encoding provided in the charset meta attribute would not be detected #3882

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7db5a01
DOC-3223: Encoding provided in the charset meta attribute would not b…
kemister85 Oct 13, 2025
41cea4b
Update modules/ROOT/pages/8.2.0-release-notes.adoc
kemister85 Oct 19, 2025
c36e6de
Merge branch 'feature/8.2.0/DOC-3223' into feature/8.2.0/DOC-3223_TIN…
kemister85 Oct 19, 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
9 changes: 8 additions & 1 deletion modules/ROOT/pages/8.2.0-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,14 @@ For information on the **Media Optimizer** plugin, see: xref:uploadcare.adoc[Med

The {productname} {release-version} release includes an accompanying release of the **Full Page HTML** premium plugin.

**Full Page HTML** includes the following improvement.
**Full Page HTML** includes the following fix.

=== Encoding provided in the charset meta attribute would not be detected
// #TINY-12860

The previous encoding detection logic did not recognize certain encodings defined using the charset `+meta+` attribute, which resulted in inconsistent or conflicting encodings within a single page and caused display or editing issues.

{productname} {release-version} addresses this issue by adding support for the new encoding type, ensuring that both the original and new encoding formats are correctly detected and processed. As a result, pages using either encoding style are now handled consistently. When encoded content is edited, the output is normalized to the previously supported encoding format, ensuring consistent markup and preventing confusion that could occur if the original encoding style were retained.

=== Head element added to the same line as the `meta` element
// #TINY-12859
Expand Down