You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DOC-3243: Errors when creating new comments made the save button stuck in a saving state. (#4030)
* Docs: DOC-3243 - Errors when creating new comments made the save button stuck in a saving state.
* Docs: DOC-3243 - Fix release note placement per review
Copy file name to clipboardExpand all lines: modules/ROOT/pages/8.4.0-release-notes.adoc
+23-16Lines changed: 23 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,21 +57,6 @@ For information on the **<Open source plugin name>** plugin, see xref:<plugincod
57
57
58
58
The following premium plugin updates were released alongside {productname} {release-version}.
59
59
60
-
=== Full Page HTML
61
-
62
-
The {productname} {release-version} release includes an accompanying release of the **Full Page HTML** premium plugin.
63
-
64
-
**Full Page HTML** includes the following addition.
65
-
66
-
==== New argument `fullpagehtml` to `editor.getContent()` and `editor.setContent()` APIs to only get/set the body of the content while the full page plugin is active.
67
-
// #TINY-13744
68
-
69
-
Previously, setting and getting the editor content while the Full Page HTML plugin was active could be troublesome due to the presence of the full HTML document on all API calls, even when not needed. Attempting to get and act only on the body content (for example, for saving) was undocumented and required workarounds.
70
-
71
-
In {productname} {release-version}, the `fullpagehtml` option has been added to the `editor.getContent()` and `editor.setContent()` APIs. When set to `false`, this option allows getting and setting only the body content while the Full Page HTML plugin is active, without interfering with the full document structure. The document is now more resistant to accidental changes, and content can be retrieved or updated without including the full HTML document. For details, see xref:fullpagehtml.adoc#fullpagehtml-getcontent-setcontent[`fullpagehtml` option for getContent/setContent].
72
-
73
-
For information on the **Full Page HTML** plugin, see: xref:fullpagehtml.adoc[Full Page HTML].
74
-
75
60
=== Media Optimizer
76
61
77
62
The {productname} {release-version} release includes an accompanying release of the **Media Optimizer** premium plugin.
@@ -91,7 +76,7 @@ For information on the **Media Optimizer** plugin, see: xref:uploadcare.adoc[Med
91
76
92
77
The {productname} {release-version} release includes an accompanying release of the **Full Page HTML** premium plugin.
93
78
94
-
**Full Page HTML** includes the following fix.
79
+
**Full Page HTML** includes the following fixes.
95
80
96
81
==== Pasting an HTML document was vulnerable to XSS attacks
97
82
// #TINY-13673
@@ -100,8 +85,30 @@ A cross-site scripting (XSS) vulnerability was discovered in the Full Page HTML
100
85
101
86
This vulnerability has been patched in {productname} {release-version} by ensuring that content in the document `<head>` is properly encoded.
102
87
88
+
==== New argument `fullpagehtml` to `editor.getContent()` and `editor.setContent()` APIs to only get/set the body of the content while the full page plugin is active.
89
+
// #TINY-13744
90
+
91
+
Previously, setting and getting the editor content while the Full Page HTML plugin was active could be troublesome due to the presence of the full HTML document on all API calls, even when not needed. Attempting to get and act only on the body content (for example, for saving) was undocumented and required workarounds.
92
+
93
+
In {productname} {release-version}, the `fullpagehtml` option has been added to the `editor.getContent()` and `editor.setContent()` APIs. When set to `false`, this option allows getting and setting only the body content while the Full Page HTML plugin is active, without interfering with the full document structure. The document is now more resistant to accidental changes, and content can be retrieved or updated without including the full HTML document. For details, see xref:fullpagehtml.adoc#fullpagehtml-getcontent-setcontent[`fullpagehtml` option for getContent/setContent].
94
+
103
95
For information on the **Full Page HTML** plugin, see: xref:fullpagehtml.adoc[Full Page HTML].
104
96
97
+
=== Comments
98
+
99
+
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
100
+
101
+
**Comments** includes the following fix.
102
+
103
+
==== Errors when creating new comments made the save button stuck in a saving state.
104
+
// #TINY-12224
105
+
106
+
Previously, when creating or editing a comment in Comments, the save button could remain in a saving state indefinitely if the save operation failed or if the component was not replaced. The saving state had no way to reset to false except by recreating the component, which misled users into thinking the operation was still in progress.
107
+
108
+
In {productname} {release-version}, the save logic now resets the saving state to false after the save operation completes, whether the operation succeeds or fails. The save button no longer remains stuck in a saving state.
109
+
110
+
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].
0 commit comments