Skip to content

DOC-3355: URIs with non-Latin1 characters were returning an error #4077

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
Apr 28, 2026
+7 −0
Merged

DOC-3355: URIs with non-Latin1 characters were returning an error #4077

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b373f5
Docs: DOC-3355 - URIs with non-Latin1 characters were returning an error
kemister85 Apr 20, 2026
e94b407
Merge branch 'feature/8.5.0/DOC-3355' into feature/8.5.0/DOC-3355_TIN…
kemister85 Apr 28, 2026
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
7 changes: 7 additions & 0 deletions modules/ROOT/pages/8.5.0-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,6 +275,13 @@ The background color of accordion items in the TinyMCE AI Review list has been u

// CCFR here.

=== URIs with non-Latin1 characters were returning an error
// #TINY-13938

Previously, inserting images with data URIs that contained non-Latin 1 characters, such as SVG data URIs with a byte order mark (BOM), caused {productname} to throw an `InvalidCharacterError`. This occurred because {productname} used the `btoa` function to encode data URIs to base64, and `btoa` does not support characters outside the Latin 1 range. The error could cause the editor to hang or fail to process the image.

In {productname} {release-version}, data URIs are now encoded using `TextEncoder` before being passed to `btoa`, ensuring that non-Latin 1 characters are handled correctly. Images with data URIs containing such characters are now processed without errors.

=== Alert and confirm dialogs were not announced properly by some screen readers
// #TINY-13812

Expand Down
Loading