From b8f7a2a43e2199a32981dd25331cde58b0b101f7 Mon Sep 17 00:00:00 2001 From: Karl Kemister-Sheppard Date: Fri, 19 Jun 2026 09:11:33 +1000 Subject: [PATCH 1/3] Docs: TINYDOC-3526 - Suggested Edits API should not be tied to the existence of the suggested edits toolbar button --- modules/ROOT/pages/8.7.0-release-notes.adoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/modules/ROOT/pages/8.7.0-release-notes.adoc b/modules/ROOT/pages/8.7.0-release-notes.adoc index 60a84540ef..608c8382bd 100644 --- a/modules/ROOT/pages/8.7.0-release-notes.adoc +++ b/modules/ROOT/pages/8.7.0-release-notes.adoc @@ -39,6 +39,21 @@ The following premium plugin updates were released alongside {productname} {rele // For information on the **** plugin, see: xref:.adoc[]. +=== Suggested Edits + +The {productname} {release-version} release includes an accompanying release of the **Suggested Edits** premium plugin. + +**Suggested Edits** includes the following fix. + +==== Suggested Edits API should not be tied to the existence of the suggested edits toolbar button +// #TINYMCE-13256 + +Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. An integration that used the API through a custom button, rather than the built-in `suggestededits` toolbar button, did not receive an update when a review finished. + +In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value returned by the `hasChanges` API changes, including when a review completes. The `hasChanges` API no longer depends on the presence of the `suggestededits` toolbar button, so a custom integration stays in sync with the document state. + +For information on the **Suggested Edits** plugin, see: xref:suggestededits.adoc[Suggested Edits]. + [[improvements]] == Improvements From f0a7d227405e2e0cdac649550b91815b65b3e83a Mon Sep 17 00:00:00 2001 From: Karl Kemister-Sheppard Date: Wed, 24 Jun 2026 15:20:15 +1000 Subject: [PATCH 2/3] Update modules/ROOT/pages/8.7.0-release-notes.adoc Co-authored-by: Mitchell Crompton --- modules/ROOT/pages/8.7.0-release-notes.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/8.7.0-release-notes.adoc b/modules/ROOT/pages/8.7.0-release-notes.adoc index 608c8382bd..2c7c28d2b6 100644 --- a/modules/ROOT/pages/8.7.0-release-notes.adoc +++ b/modules/ROOT/pages/8.7.0-release-notes.adoc @@ -48,7 +48,7 @@ The {productname} {release-version} release includes an accompanying release of ==== Suggested Edits API should not be tied to the existence of the suggested edits toolbar button // #TINYMCE-13256 -Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. An integration that used the API through a custom button, rather than the built-in `suggestededits` toolbar button, did not receive an update when a review finished. +Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. As a result, any integration that relied upon the API would not receive an update when a review finished. In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value returned by the `hasChanges` API changes, including when a review completes. The `hasChanges` API no longer depends on the presence of the `suggestededits` toolbar button, so a custom integration stays in sync with the document state. From b8c979ea33052b293c1dc719eee6734dd230d29f Mon Sep 17 00:00:00 2001 From: Karl Kemister-Sheppard Date: Wed, 24 Jun 2026 15:20:32 +1000 Subject: [PATCH 3/3] Update modules/ROOT/pages/8.7.0-release-notes.adoc Co-authored-by: Mitchell Crompton --- modules/ROOT/pages/8.7.0-release-notes.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/8.7.0-release-notes.adoc b/modules/ROOT/pages/8.7.0-release-notes.adoc index 2c7c28d2b6..eff14fee57 100644 --- a/modules/ROOT/pages/8.7.0-release-notes.adoc +++ b/modules/ROOT/pages/8.7.0-release-notes.adoc @@ -50,7 +50,7 @@ The {productname} {release-version} release includes an accompanying release of Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. As a result, any integration that relied upon the API would not receive an update when a review finished. -In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value returned by the `hasChanges` API changes, including when a review completes. The `hasChanges` API no longer depends on the presence of the `suggestededits` toolbar button, so a custom integration stays in sync with the document state. +In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value within the `hasChanges` API changes, including when a review completes. For information on the **Suggested Edits** plugin, see: xref:suggestededits.adoc[Suggested Edits].