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
{productname} {release-version} was released for {enterpriseversion} and {cloudname} on Wednesday, September 10^th^, 2025. These release notes provide an overview of the changes for {productname} {release-version}, including:
14
+
{productname} {release-version} was released for {enterpriseversion} and {cloudname} on Wednesday, September 17^th^, 2025. These release notes provide an overview of the changes for {productname} {release-version}, including:
@@ -42,34 +40,6 @@ The following new Premium plugin was released alongside {productname} {release-v
42
40
43
41
The following premium plugin updates were released alongside {productname} {release-version}.
44
42
45
-
// === <Premium plugin name 1> <Premium plugin name 1 version>
46
-
47
-
// The {productname} {release-version} release includes an accompanying release of the **<Premium plugin name 1>** premium plugin.
48
-
49
-
// **<Premium plugin name 1>** <Premium plugin name 1 version> includes the following <fixes, changes, improvements>.
50
-
51
-
// ==== <Premium plugin name 1 change 1>
52
-
53
-
// CCFR here.
54
-
55
-
// For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
56
-
57
-
=== Accessibility Checker
58
-
59
-
The {productname} {release-version} release includes an accompanying release of the **Accessibility Checker** premium plugin.
60
-
61
-
**Accessibility Checker** includes the following improvement.
62
-
63
-
==== Auto-suggest `+alt+` text from existing `+alt+`, `+aria-label+`, and `+title+` attributes with priority fallback in image repair dialogs.
64
-
// #TINY-12547
65
-
66
-
In previous version of **Accessibility Checker**, the image repair dialog only proposed values from `+alt+`, ignoring `+aria-label+` and `+title+`, which forced manual entry and slowed accessibility repairs while increasing the risk of inconsistent descriptions.
67
-
68
-
{productname} {release-version} now auto-suggests `+alt+` text using a priority-based fallback that checks existing attributes in order `+aria-labelledby+`, `+aria-label+`, `+alt+` then `+title+` and leaves the field empty if none are present. This ensures that users can label images faster and with greater accuracy by leveraging existing accessibility attributes, improving repair efficiency and consistency.
69
-
70
-
For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.adoc[Accessibility Checker].
71
-
72
-
73
43
=== Spell Checker
74
44
75
45
The {productname} {release-version} release includes an accompanying release of the **Spell Checker** premium plugin.
@@ -85,22 +55,6 @@ To resolve this, {productname} now inserts a temporary hidden element before the
85
55
86
56
For information on the **Spell Checker** plugin, see: xref:introduction-to-tiny-spellchecker.adoc[Spell Checker].
87
57
88
-
=== Comments
89
-
90
-
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
91
-
92
-
**Comments** Premium plugin includes the following removal.
93
-
94
-
==== Improved keyboard navigation in Comments dropdown when inserting `@Mention`
95
-
// #TINY-12785
96
-
97
-
Previously, typing `@` to open the mentions dropdown list inside the Comments card did not support the **Shift+Enter** keyboard combination. For example, when typing a `@` + navigating to a user in the selected Comment card, pressing **Shift+Enter** did not insert the `@mention` to the `<textarea>` for the comment body.
98
-
99
-
In {productname} {release-version}, this issue has been resolved by handling **Shift+Enter** in the same way as the regular **Enter** key, ensuring consistent and predictable keyboard interaction when selecting items in the `@mentions` dropdown within comment cards.
100
-
101
-
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to Tiny Comments].
102
-
103
-
104
58
=== Image Optimizer (Powered by Uploadcare)
105
59
106
60
The {productname} {release-version} release includes an accompanying release of the **Image Optimizer (Powered by Uploadcare)** premium plugin.
@@ -119,7 +73,7 @@ For information on the **Image Optimizer Powered by Uploadcare** plugin, see: xr
119
73
120
74
The {productname} {release-version} release includes an accompanying release of the **Accessibility Checker** premium plugin.
121
75
122
-
**Accessibility Checker** includes the following improvement.
76
+
**Accessibility Checker** includes the following improvements.
123
77
124
78
==== `+alt+` text length error message now shows current and maximum character counts
125
79
// #TINY-12569
@@ -128,6 +82,13 @@ Previous versions of **Accessibility Checker**, the `+alt+` text length validati
128
82
129
83
In {productname} {release-version}, the error message for **Accessibility Checker** has been updated to show both the current and maximum character counts, for example: "_151 characters (maximum 150 allowed)_." This improvement provides clear, actionable error messaging that aligns with accessibility guidance and reduces user confusion across all affected rules.
130
84
85
+
==== Auto-suggest `+alt+` text from existing `+alt+`, `+aria-label+`, and `+title+` attributes with priority fallback in image repair dialogs.
86
+
// #TINY-12547
87
+
88
+
In previous version of **Accessibility Checker**, the image repair dialog only proposed values from `+alt+`, ignoring `+aria-label+` and `+title+`, which forced manual entry and slowed accessibility repairs while increasing the risk of inconsistent descriptions.
89
+
90
+
{productname} {release-version} now auto-suggests `+alt+` text using a priority-based fallback that checks existing attributes in order `+aria-labelledby+`, `+aria-label+`, `+alt+` then `+title+` and leaves the field empty if none are present. This ensures that users can label images faster and with greater accuracy by leveraging existing accessibility attributes, improving repair efficiency and consistency.
91
+
131
92
For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.adoc[Accessibility Checker].
132
93
133
94
=== Revision History
@@ -154,7 +115,7 @@ For information on the **Revision History** plugin, see: xref:revisionhistory.ad
154
115
155
116
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
156
117
157
-
**Comments** Premium plugin includes the following fixes and improvement.
118
+
**Comments** Premium plugin includes the following fixes and improvement and removal.
158
119
159
120
==== Default avatars generated inconsistently
160
121
// The same user avatar was generated for all users without an avatar in the mentions dropdown.
@@ -164,6 +125,13 @@ The {productname} {release-version} release includes an accompanying release of
164
125
165
126
Previously, {productname} generated default avatars inconsistently in the Comments plugin. Users without avatars saw the same placeholder avatar in the mentions dropdown, while the same individual could also receive different default avatars in other contexts. This inconsistency made it difficult to distinguish users and, in some cases, created confusion by making a single user appear as two different people. In {release-version}, this issue has been fixed, and default avatars are now consistently generated with a stable color based on the `+user_id+`. This ensures that the same user always has the same default avatar, improving clarity and providing a more reliable user experience.
166
127
128
+
==== Improved keyboard navigation in Comments dropdown when inserting `@Mention`
129
+
// #TINY-12785
130
+
131
+
Previously, typing `@` to open the mentions dropdown list inside the Comments card did not support the **Shift+Enter** keyboard combination. For example, when typing a `@` + navigating to a user in the selected Comment card, pressing **Shift+Enter** did not insert the `@mention` to the `<textarea>` for the comment body.
132
+
133
+
In {productname} {release-version}, this issue has been resolved by handling **Shift+Enter** in the same way as the regular **Enter** key, ensuring consistent and predictable keyboard interaction when selecting items in the `@mentions` dropdown within comment cards.
134
+
167
135
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to Tiny Comments].
168
136
169
137
=== Mentions
@@ -200,22 +168,13 @@ For information on the **AI Assistant** plugin, see: xref:ai.adoc[AI Assistant],
200
168
201
169
The {productname} {release-version} release includes an accompanying release of the **Suggested Edits** premium plugin.
202
170
203
-
**Suggested Edits** includes the following improvement.
171
+
**Suggested Edits** includes the following fix andimprovement.
204
172
205
173
==== Added keyboard navigation to the Suggested Edits plugin
206
174
// #TINY-11452
207
175
208
176
The initial release of the Suggested Edits plugin did not support keyboard navigation, limiting accessibility for users who rely on keyboard-based interactions. This restriction made it difficult to move through and interact with the suggested edits sidebar and cards without using a mouse. To improve usability and accessibility, keyboard navigation has been implemented in the Suggested Edits plugin. Users can now efficiently navigate and interact with the plugin using the keyboard.
209
177
210
-
For information on the **Suggested Edits** plugin, see: xref:suggestededits.adoc[Suggested Edits].
211
-
212
-
213
-
=== Suggested Edits
214
-
215
-
The {productname} {release-version} release includes an accompanying release of the **Suggested Edits** premium plugin.
216
-
217
-
**Suggested Edits** includes the following fix:
218
-
219
178
=== Empty editor operations sometimes showed as modified instead of added/removed
220
179
// #TINY-12273
221
180
@@ -229,12 +188,7 @@ For information on the **Suggested Edits** plugin, see: xref:suggestededits.adoc
229
188
[[improvements]]
230
189
== Improvements
231
190
232
-
{productname} {release-version} also includes the following improvement<s>:
233
-
234
-
// === <TINY-vwxyz 1 changelog entry>
235
-
// #TINY-vwxyz1
236
-
237
-
// CCFR here.
191
+
{productname} {release-version} also includes the following improvements:
238
192
239
193
=== `editor.getContent()` now includes `indent` and `entity_encoding` properties to control HTML formatting
240
194
// #TINY-12786
@@ -284,26 +238,10 @@ Previously, and issue was identified where clicking the editor's horizontal scro
284
238
{productname} {release-version} addresses this issue. Now, the editor avoids taking focus when users click elements that are not selectable (such as scrollbars), preventing unintended vertical scrolling.
285
239
286
240
287
-
[[additions]]
288
-
== Additions
289
-
290
-
{productname} {release-version} also includes the following addition<s>:
291
-
292
-
// === <TINY-vwxyz 1 changelog entry>
293
-
// #TINY-vwxyz1
294
-
295
-
// CCFR here.
296
-
297
-
298
241
[[changes]]
299
242
== Changes
300
243
301
-
{productname} {release-version} also includes the following change<s>:
302
-
303
-
// === <TINY-vwxyz 1 changelog entry>
304
-
// #TINY-vwxyz1
305
-
306
-
// CCFR here.
244
+
{productname} {release-version} also includes the following change:
307
245
308
246
=== Tooltips can now remain open when hovered
309
247
// #TINY-12053
@@ -313,26 +251,11 @@ Previously, tooltips would disappear when the cursor moved from the toolbar butt
313
251
This improvement addresses the link:https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus[WCAG 2.1 Success Criterion 1.4.13: Content on Hover or Focus (Level AA)], specifically the "Hoverable" requirement.
314
252
315
253
316
-
[[removed]]
317
-
== Removed
318
-
319
-
{productname} {release-version} also includes the following removal<s>:
320
-
321
-
// === <TINY-vwxyz 1 changelog entry>
322
-
// #TINY-vwxyz1
323
-
324
-
// CCFR here.
325
-
326
-
327
254
[[bug-fixes]]
328
255
== Bug fixes
329
256
330
-
{productname} {release-version} also includes the following bug fix<es>:
331
-
332
-
// === <TINY-vwxyz 1 changelog entry>
333
-
// #TINY-vwxyz1
257
+
{productname} {release-version} also includes the following bug fixes:
334
258
335
-
// CCFR here.
336
259
=== NVDA would announce iframe_aria_text multiple times
This caused issues when opening such links, as the URLs became invalid. In {release-version}, {productname} now automatically decodes `+&+` back to `+&+` before inserting the link, ensuring that pasted URLs remain valid and functional in both the editor and the source code.
386
309
387
310
388
-
[[security-fixes]]
389
-
== Security fixes
390
-
391
-
{productname} {release-version} includes <a fix | fixes for the following security issue<s>:
Copy file name to clipboardExpand all lines: modules/ROOT/pages/changelog.adoc
+34-2Lines changed: 34 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,41 @@
5
5
NOTE: This is the {productname} Community version changelog. For information about the latest {cloudname} or {enterpriseversion} Release, see: xref:release-notes.adoc[{productname} Release Notes].
0 commit comments