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
Docs: DOC-3355 - Clean up 8.5.0 release notes, changelog, and nav
- Fix grammar, punctuation, and spelling across release notes
- Resolve plural markers and remove trailing periods from headings
- Add missing Changed and Deprecated entries to changelog
- Align bug fix order between changelog and release notes
- Remove unused Security fixes, Known issues, and Removed nav entries
- Add spellchecker_language deprecation to release notes and changelog
The following premium plugin updates were released alongside {productname} {release-version}.
31
29
32
-
=== <Premium plugin name 1> <Premium plugin name 1 version>
33
-
34
-
The {productname} {release-version} release includes an accompanying release of the **<Premium plugin name 1>** premium plugin.
35
-
36
-
**<Premium plugin name 1>** <Premium plugin name 1 version> includes the following <fixes, changes, improvements>.
37
-
38
-
==== <Premium plugin name 1 change 1>
39
-
40
-
// CCFR here.
41
-
42
-
For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
43
-
44
30
=== Spell Checker
45
31
46
32
The {productname} {release-version} release includes an accompanying release of the **Spell Checker** premium plugin.
@@ -62,7 +48,7 @@ The {productname} {release-version} release includes an accompanying release of
62
48
63
49
**Accessibility Checker** includes the following fix.
64
50
65
-
==== Accessibility checker overlay was too dark on multiline inline elements
51
+
==== Accessibility Checker overlay was too dark on multiline inline elements
66
52
// #TINY-14246
67
53
68
54
Previously, when the Accessibility Checker highlighted multiline inline elements, the overlay effect appeared excessively dark. The box-shadow dimming applied to these elements stacked across multiple lines, making the highlighted content difficult to read.
@@ -137,7 +123,7 @@ For information on the **Suggested Edits** plugin, see: xref:suggestededits.adoc
137
123
138
124
The {productname} {release-version} release includes an accompanying release of the **TinyMCE AI** premium plugin.
139
125
140
-
**TinyMCE AI** includes the following fixes, improvements and additions.
126
+
**TinyMCE AI** includes the following fixes, improvements, and additions.
141
127
142
128
==== A long list of fetched sources could overflow the submenu in the AI chat without a way to scroll
143
129
// #TINY-14064
@@ -146,7 +132,7 @@ Previously, when the list of fetched sources returned from the AI chat exceeded
146
132
147
133
In {productname} {release-version}, the AI chat source submenu includes a maximum height constraint and scrollbar support. Long lists of fetched sources now display within a scrollable area, allowing access to all sources regardless of list length.
148
134
149
-
==== In some browser/OS combinations it was not possible to have 3 source tags in the same row because of the scrollbar
135
+
==== In some browser/OS combinations, it was not possible to have 3 source tags in the same row because of the scrollbar
150
136
// #TINY-14156
151
137
152
138
Previously, in the TinyMCE AI Chat panel, source tags displayed in the response area could appear in rows of only two instead of three on certain browser and operating system combinations. The `max-width` of the source tags did not account for the additional space consumed by thicker scrollbars on some platforms, causing the third tag to wrap to the next row.
@@ -182,7 +168,7 @@ Previously, renaming a conversation in the TinyMCE AI Chat History panel preserv
182
168
183
169
In {productname} {release-version}, conversation titles are now trimmed on save, removing any leading and trailing whitespace before the name is stored. Titles display consistently in the Chat History panel without unintended spacing.
184
170
185
-
==== It was possible to submit white space only titles when renaming a conversation
171
+
==== It was possible to submit whitespace-only titles when renaming a conversation
186
172
// #TINY-14251
187
173
188
174
Previously, in the TinyMCE AI Chat History panel, renaming a conversation and clearing the title field would correctly disable the Save button. However, pressing Enter while the input was empty or contained only whitespace bypassed the disabled button and submitted the empty title. This resulted in conversations being saved with blank names, making them difficult to identify in the history.
@@ -196,7 +182,7 @@ Previously, switching between preview and diff modes in the TinyMCE AI review pa
196
182
197
183
In {productname} {release-version}, the active suggestion is now preserved when switching between preview and diff modes. Users return to the same suggestion they were viewing prior to the mode change, and manually scrolling in preview mode no longer forces the view to jump when switching back to diff mode.
198
184
199
-
==== Improved error message for too-large prompts.
185
+
==== Improved error message for too-large prompts
200
186
// #TINY-14104
201
187
202
188
Previously, when a prompt sent to the TinyMCE AI service exceeded size limits, the error message did not include enough detail for integrators to diagnose the issue. The structured error data returned by the service, such as the current prompt length and the maximum allowed length, was not decoded or displayed.
@@ -261,7 +247,7 @@ Previously, the actions container in the TinyMCE AI Chat History panel had no re
261
247
262
248
In {productname} {release-version}, the actions container now reserves minimum horizontal space to accommodate the icon button and its surrounding padding. Action buttons appear and disappear without causing layout shifts, providing smoother and more predictable interactions with the Chat History.
263
249
264
-
==== Focus is no longer lost when deleting a context source using delete or backspace key.
250
+
==== Focus is no longer lost when deleting a context source using the Delete or Backspace key
265
251
// #TINY-13949
266
252
267
253
Previously, keyboard focus was lost when deleting a context source tag using the `Delete` or `Backspace` key in the TinyMCE AI sidebar chat view. After removing a context source, the focus disappeared entirely, making it difficult to continue keyboard navigation. This particularly affected accessibility and keyboard-only workflows.
@@ -275,14 +261,14 @@ Previously, the `+ToggleSidebar+` event was not emitted when opening or closing
275
261
276
262
In {productname} {release-version}, floating sidebars now fully support the existing sidebar APIs. The `+ToggleSidebar+` event fires when floating sidebars are opened, closed, or switched, and `+queryCommandValue+` returns the correct sidebar identifier. This brings floating sidebars to full API parity with regular sidebars.
277
263
278
-
==== AI Review suggestion cards now stay available when you close and reopen the review sidebar while suggestions are still loading
264
+
==== AI Review suggestion cards now stay available when the review sidebar is closed and reopened while suggestions are still loading
279
265
// #TINY-14197
280
266
281
267
Previously, closing the TinyMCE AI Review sidebar immediately after starting a review and then reopening it after the AI finished generating suggestions would reset the sidebar state. The suggestion cards associated with the review were not displayed, and instead the list of available reviews appeared alongside the preview. This prevented the generated suggestions from being actioned.
282
268
283
269
In {productname} {release-version}, the sidebar state is now correctly preserved when the sidebar is closed and reopened during or after suggestion generation. The review suggestion cards remain visible and actionable, even if the sidebar was closed while the AI was still streaming results.
284
270
285
-
==== Menus no longer close on mouse out.
271
+
==== Menus no longer close on mouse out
286
272
// #TINY-14055
287
273
288
274
Previously, submenus in the TinyMCE AI plugin closed when the mouse pointer moved outside the menu area. This did not match the behavior of other {productname} menus, where submenus remain open until another item in the parent menu is selected or the entire menu is dismissed. The inconsistency made submenu navigation unreliable and could cause confusion during use.
@@ -303,7 +289,7 @@ Previously, Quick Actions in TinyMCE AI could only be triggered through the plug
303
289
304
290
In {productname} {release-version}, the TinyMCE AI plugin registers a set of editor commands that mirror each Quick Action. These include commands for built-in actions such as `TinyMCEAIQuickActionImproveWriting`, `TinyMCEAIQuickActionCheckGrammar`, and `TinyMCEAIQuickActionTranslate` (which accepts a language argument), as well as `TinyMCEAIQuickActionCustom` for running a custom prompt with a specified model. A `TinyMCEAIChatPrompt` command is also available for sending a prompt directly to the Chat sidebar. For the full list of commands, see xref:tinymceai.adoc#tinymceai-plugin-commands[TinyMCE AI plugin commands].
305
291
306
-
==== New optional `id` property to `tinymceai_quickactions_custom` to register the action as custom menu item
292
+
==== New optional `id` property to `tinymceai_quickactions_custom` to register the action as a custom menu item
307
293
// #TINY-14229
308
294
309
295
Previously, custom quick actions defined through the xref:tinymceai.adoc#tinymceai_quickactions_custom[`+tinymceai_quickactions_custom+`] option could only appear inside a dedicated Custom submenu within the Quick Actions menu. This limited integrators who wanted custom actions to appear as top-level menu items alongside predefined actions or in other menu configurations.
@@ -334,7 +320,7 @@ The {productname} {release-version} release includes an accompanying release of
334
320
335
321
=== Enhanced Skins & Icon Packs
336
322
337
-
The **Enhanced Skins & Icon Packs** release includes the following updates and fix.
323
+
The **Enhanced Skins & Icon Packs** release includes the following updates and fixes.
338
324
339
325
The **Enhanced Skins & Icon Packs** were rebuilt to pull in the changes also incorporated into the default {productname} {release-version} skin, Oxide.
340
326
@@ -358,14 +344,9 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
358
344
[[improvements]]
359
345
== Improvements
360
346
361
-
{productname} {release-version} also includes the following improvement<s>:
362
-
363
-
=== <TINY-vwxyz 1 changelog entry>
364
-
// #TINY-vwxyz1
365
-
366
-
// CCFR here.
347
+
{productname} {release-version} also includes the following improvement:
367
348
368
-
=== Improved visual styling of inline diff highlights in Suggested Edits and TinyMCE AI plugin.
349
+
=== Improved visual styling of inline diff highlights in Suggested Edits and TinyMCE AI plugin
369
350
// #TINY-13958
370
351
371
352
Previously, when diff highlights were selected in the Suggested Edits and TinyMCE AI plugins, the visual styling produced overlapping effects that cluttered the display. Multiple style layers, including borders, box shadows, and background colors, combined to obscure the highlighted content. This made it difficult to read and review suggested changes, particularly for inline text elements spanning multiple lines.
@@ -376,12 +357,7 @@ In {productname} {release-version}, the visual styling for selected diff highlig
376
357
[[additions]]
377
358
== Additions
378
359
379
-
{productname} {release-version} also includes the following addition<s>:
380
-
381
-
=== <TINY-vwxyz 1 changelog entry>
382
-
// #TINY-vwxyz1
383
-
384
-
// CCFR here.
360
+
{productname} {release-version} also includes the following addition:
385
361
386
362
=== New `content_language` option to set the `lang` attribute on the iframe's `html` element or the inline editor's target element
387
363
// #TINY-11214
@@ -394,46 +370,25 @@ In {productname} {release-version}, the new xref:content-localization.adoc#conte
394
370
[[changes]]
395
371
== Changes
396
372
397
-
{productname} {release-version} also includes the following change<s>:
398
-
399
-
=== <TINY-vwxyz 1 changelog entry>
400
-
// #TINY-vwxyz1
401
-
402
-
// CCFR here.
373
+
{productname} {release-version} also includes the following change:
403
374
404
375
=== Updated the Review list accordion item background color
405
376
// #TINY-14158
406
377
407
378
The background color of accordion items in the TinyMCE AI Review list has been updated from `#F7F7F7` to `#F0F0F0` to improve visual contrast and align with the current design specifications.
408
379
409
380
410
-
[[removed]]
411
-
== Removed
412
-
413
-
{productname} {release-version} also includes the following removal<s>:
414
-
415
-
=== <TINY-vwxyz 1 changelog entry>
416
-
// #TINY-vwxyz1
417
-
418
-
// CCFR here.
419
-
420
-
421
381
[[bug-fixes]]
422
382
== Bug fixes
423
383
424
-
{productname} {release-version} also includes the following bug fix<es>:
425
-
426
-
=== <TINY-vwxyz 1 changelog entry>
427
-
// #TINY-vwxyz1
428
-
429
-
// CCFR here.
384
+
{productname} {release-version} also includes the following bug fixes:
430
385
431
386
=== URIs with non-Latin1 characters were returning an error
432
387
// #TINY-13938
433
388
434
-
Previously, inserting images with data URIs that contained non-Latin 1 characters, such as SVG data URIs with a byte order mark (BOM), caused {productname} to throw an `InvalidCharacterError`. This occurred because {productname} used the `btoa` function to encode data URIs to base64, and `btoa` does not support characters outside the Latin 1 range. The error could cause the editor to hang or fail to process the image.
389
+
Previously, inserting images with data URIs that contained non-Latin 1 characters, such as SVG data URIs with a byte order mark (BOM), caused {productname} to throw an `InvalidCharacterError`. This occurred because {productname} used the `btoa` function to encode data URIs to base64, and `btoa` does not support characters outside the Latin1 range. The error could cause the editor to hang or fail to process the image.
435
390
436
-
In {productname} {release-version}, data URIs are now encoded using `TextEncoder` before being passed to `btoa`, ensuring that non-Latin 1 characters are handled correctly. Images with data URIs containing such characters are now processed without errors.
391
+
In {productname} {release-version}, data URIs are now encoded using `TextEncoder` before being passed to `btoa`, ensuring that non-Latin1 characters are handled correctly. Images with data URIs containing such characters are now processed without errors.
437
392
438
393
=== Alert and confirm dialogs were not announced properly by some screen readers
439
394
// #TINY-13812
@@ -471,35 +426,14 @@ Previously, `iframe` elements that contained child nodes were removed entirely d
471
426
In {productname} {release-version}, `iframe` elements are preserved during sanitization. Any child nodes and unsafe or invalid attributes are removed, but the `iframe` element itself remains in the editor content.
472
427
473
428
474
-
[[security-fixes]]
475
-
== Security fixes
476
-
477
-
{productname} {release-version} includes <a fix | fixes for the following security issue<s>:
478
-
479
-
=== <TINY-vwxyz 1 changelog entry>
480
-
// #TINY-vwxyz1
481
-
482
-
// CCFR here.
483
-
484
-
485
429
[[deprecated]]
486
430
== Deprecated
487
431
488
-
{productname} {release-version} includes the following deprecation<s>:
489
-
490
-
=== The `<plugin>` configuration property, `<name>`, has been deprecated
491
-
492
-
// placeholder here.
493
-
432
+
{productname} {release-version} includes the following deprecation:
494
433
495
-
[[known-issues]]
496
-
== Known issues
497
-
498
-
This section describes issues that users of {productname} {release-version} may encounter and possible workarounds for these issues.
499
-
500
-
There <is one | are <number> known issue<s> in {productname} {release-version}.
434
+
=== The Spell Checker configuration property, `spellchecker_language`, has been deprecated
435
+
// #TINY-11214
501
436
502
-
=== <TINY-vwxyz 1 changelog entry>
503
-
// #TINY-vwxyz1
437
+
The `+spellchecker_language+` option has been deprecated as of {productname} {release-version} and will be removed in a future major release. Use xref:content-localization.adoc#content_language[`+content_language+`] instead, which sets both the default content language and the Spell Checker proofing language.
504
438
505
-
// CCFR here.
439
+
For information on the `+content_language+` option, see: xref:content-localization.adoc#content_language[Content localization].
0 commit comments