Skip to content

TINYDOC-3528: Clicking the reply button triggered an editor blur event #4271

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

Open
kemister85 wants to merge 2 commits into
base: feature/8.8.0/TINYDOC-3528
Choose a base branch
from
+15 −0
Open

TINYDOC-3528: Clicking the reply button triggered an editor blur event #4271

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fb2926b
Docs: TINYDOC-3528 - Clicking the reply button triggered an editor bl…
kemister85 Jul 9, 2026
d50849d
Docs: TINYDOC-3528 - Reference the concrete reply count button in the…
kemister85 Jul 9, 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
15 changes: 15 additions & 0 deletions modules/ROOT/pages/8.8.0-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,21 @@ The {productname} {release-version} release includes an accompanying release of

For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].

=== Comments

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

**Comments** includes the following fix.

==== Clicking the reply button triggered an editor blur event
// #TINYMCE-12236

Previously, selecting the reply count button on a comment thread, such as *1 reply*, could cause the editor to fire a `+blur+` event, even though focus remained within the editor. Expanding the replies re-rendered the comment and moved focus to the editor content, which the editor interpreted as focus leaving the editor. Applications that rely on the `+blur+` event to detect when editing has finished could behave incorrectly.

@lorenzo-pomili lorenzo-pomili Jul 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Expanding the replies re-rendered the comment and moved focus to the editor content

actually the pre-fix behaviour was that the focus were lost entirely


In {productname} {release-version}, the Comments plugin preserves editor focus when expanding replies. The editor no longer fires an unexpected `+blur+` event when the reply button is selected.

For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].


[[accompanying-premium-plugin-end-of-life-announcement]]
== Accompanying Premium plugin end-of-life announcement
Expand Down
Loading