Skip to content

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

Open
kemister85 wants to merge 2 commits into
feature/8.8.0/TINYDOC-3528from
feature/8.8.0/TINYDOC-3528_TINYMCE-12236
Open

TINYDOC-3528: Clicking the reply button triggered an editor blur event#4271
kemister85 wants to merge 2 commits into
feature/8.8.0/TINYDOC-3528from
feature/8.8.0/TINYDOC-3528_TINYMCE-12236

Conversation

@kemister85

@kemister85 kemister85 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Ticket: TINYDOC-3528 (TINYMCE-12236)

Site: Staging

Changes:

  • Added a release note entry for TINYMCE-12236 to modules/ROOT/pages/8.8.0-release-notes.adoc (Accompanying Premium plugin changes → Comments): Clicking the reply button triggered an editor blur event.

Pre-checks:

  • Branch is correctly prefixed (release-note branch)
  • modules/ROOT/nav.adoc has been updated (if applicable).
  • Files have been included where required (if applicable).
  • Files removed have been deleted, not just excluded from the build (if applicable).
  • Files added for New product features include a release note entry.
  • Major or minor version changes have updated the supported-versions.adoc table.
  • Build passes without console errors, warnings, or issues.

@kemister85 kemister85 added this to the TinyMCE 8.8.0 milestone Jul 9, 2026
@kemister85 kemister85 added the upcoming release Documentation for features currently under development/QA label Jul 9, 2026
@kemister85 kemister85 requested a review from lorenzo-pomili July 9, 2026 07:27
@kemister85 kemister85 marked this pull request as ready for review July 9, 2026 07:27
@kemister85 kemister85 requested review from a team and soritaheng as code owners July 9, 2026 07:27
@kemister85 kemister85 requested review from MitchC1999, ShiridiGandham and tiny-ben-tran and removed request for a team July 9, 2026 07:27
==== 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.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

upcoming release Documentation for features currently under development/QA

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants