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
The following premium plugin updates were released alongside {productname} {release-version}.
30
30
31
+
=== TinyMCE AI
32
+
33
+
The {productname} {release-version} release includes an accompanying release of the **TinyMCE AI** premium plugin.
34
+
35
+
**TinyMCE AI** includes the following fix.
36
+
37
+
==== Image edits now target the correct image in content with multiple images
38
+
// #TINY-14454
39
+
40
+
Previously, images sent to the model were not uniquely identified, so a prompt referencing a specific image could mistake one image for another and apply changes, such as alt text updates, to the wrong image. **TinyMCE AI** now uniquely tags each `+img+` elements so they are less likely to be mistaken. Image edits now apply to the intended image, even when the content contains multiple images.
41
+
42
+
For information on the **TinyMCE AI** plugin, see: xref:tinymceai.adoc[TinyMCE AI].
43
+
31
44
// === <Premium plugin name 1> <Premium plugin name 1 version>
32
45
33
46
// The {productname} {release-version} release includes an accompanying release of the **<Premium plugin name 1>** premium plugin.
@@ -39,6 +52,71 @@ The following premium plugin updates were released alongside {productname} {rele
39
52
40
53
// For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
41
54
55
+
=== Inline CSS
56
+
57
+
The {productname} {release-version} release includes an accompanying release of the **Inline CSS** premium plugin.
58
+
59
+
**Inline CSS** includes the following fix.
60
+
61
+
==== The fullpage header and footer were not included when getting HTML content with inline CSS
62
+
// #TINY-14410
63
+
64
+
Previously, the **Inline CSS** plugin's `getContent` API did not return a complete HTML document when the **Full Page HTML** plugin was enabled. The surrounding document header and footer were omitted, which made the output unsuitable for use cases such as generating email-ready documents.
65
+
66
+
In {productname} {release-version}, the **Inline CSS** plugin detects when the **Full Page HTML** plugin is enabled and includes the document header and footer in its output. The `getContent` API now returns a full HTML document as expected.
67
+
68
+
For information on the **Inline CSS** plugin, see: xref:inline-css.adoc[Inline CSS].
69
+
70
+
=== TinyMCE AI
71
+
72
+
The {productname} {release-version} release includes an accompanying release of the **TinyMCE AI** premium plugin.
73
+
74
+
**TinyMCE AI** includes the following improvements and fixes and additions.
75
+
76
+
==== Keyboard navigation in the preview footer now focuses the currently active view mode instead of always the first one
77
+
// #TINY-14272
78
+
79
+
Previously, moving keyboard focus to the preview footer in the AI Chat always landed on the first view mode option rather than the one that was currently active. This made keyboard navigation between the Diff mode and Preview tabs less predictable.
80
+
81
+
In {productname} {release-version}, focus moves to the currently active view mode in the preview footer. Keyboard navigation now reflects the active selection.
82
+
83
+
==== A confirmation dialog now appears before navigating away from unresolved suggestions, such as when switching to another sidebar or opening a sidebar during quick actions
84
+
// #TINY-14236
85
+
86
+
Previously, switching between the AI Chat and Review sidebars, or opening a sidebar during quick actions, while AI suggestions were still unresolved discarded those suggestions and any applied changes permanently. A single accidental click could cause lost progress.
87
+
88
+
In {productname} {release-version}, a confirmation dialog appears before navigating away from unresolved suggestions. The action proceeds only after it is confirmed, which prevents the accidental loss of in-progress changes.
89
+
90
+
==== Two tooltips were shown at the same time when hovering over context sources or conversation titles that were shortened with an ellipsis in Safari
91
+
// #TINY-14032
92
+
93
+
Previously, in Safari, hovering over text that was shortened with an ellipsis, such as AI Chat conversation titles or context sources, could display two tooltips at once: the browser's native tooltip and the plugin's custom tooltip.
94
+
95
+
In {productname} {release-version}, only the native tooltip is shown for these elements in Safari. A single tooltip now appears on hover as expected.
96
+
97
+
==== An error could be reported when aborting and starting a new conversation
98
+
// #TINY-14381
99
+
100
+
Previously, aborting a streamed AI response and starting a new conversation could report an error. Aborting the response triggered a document delete operation that sometimes failed.
101
+
102
+
In {productname} {release-version}, the document is no longer deleted when an AI request is aborted. Aborting a response and starting a new conversation no longer reports this error.
103
+
104
+
==== AI response HTML is now filtered through the editor's content pipeline before being displayed in preview
105
+
// #TINY-14344
106
+
107
+
Previously, content shown in the AI preview was not filtered by the editor's content rules until it was applied. With a strict schema configuration, a change could appear in the preview, be accepted, and then be removed when applied to the editor, so the final result did not match the preview.
108
+
109
+
In {productname} {release-version}, AI response HTML is filtered through the editor's content pipeline before it is shown in the preview. The preview now reflects what will be added to the editor, and if filtering removes all of the content the user is notified.
110
+
111
+
==== AI Chat state was lost if the sidebar was closed before the model started responding
112
+
// #TINY-14222
113
+
114
+
Previously, the state of an AI Chat conversation could be lost if the Chat sidebar was closed before the model began responding to a prompt. The plugin recorded which sidebar started a response only once the response began, so closing the sidebar beforehand left no record. Reopening the sidebar then reset the conversation and any pending preview.
115
+
116
+
In {productname} {release-version}, the sidebar is recorded as soon as the prompt is sent. Closing and reopening the Chat sidebar before the response is ready no longer resets the conversation.
117
+
118
+
For information on the **TinyMCE AI** plugin, see: xref:tinymceai.adoc[TinyMCE AI].
119
+
42
120
43
121
[[improvements]]
44
122
== Improvements
@@ -50,6 +128,20 @@ The following premium plugin updates were released alongside {productname} {rele
50
128
51
129
// CCFR here.
52
130
131
+
=== Pressing Tab or Shift+Tab on an open menu now closes it and moves focus to the next or previous focusable element
132
+
// #TINY-13341
133
+
134
+
Previously, pressing Tab or Shift+Tab inside an open dropdown menu cycled focus through the menu items instead of closing the menu. This behavior did not align with accessibility guidelines, which recommend that the Tab key close the menu and move focus to the next or previous element in the tab order. As a result, keyboard navigation through menus was less predictable for users who rely on the keyboard or assistive technologies.
135
+
136
+
In {productname} {release-version}, pressing Tab or Shift+Tab on an open menu now closes the menu and moves focus to the next or previous focusable element in the tab order. This makes keyboard navigation more predictable and aligns dropdown menu behavior with accessibility guidelines.
137
+
138
+
=== The editor resize handle now uses browser pointer events for more reliable behavior across different integration environments
139
+
// #TINY-14241
140
+
141
+
Previously, the editor resize handle relied on an overlay element to capture pointer movement, which required raising the editor's stacking order. This caused the editor to appear on top of the floating sidebar used by the TinyMCE AI plugin while the editor was being resized.
142
+
143
+
In {productname} {release-version}, the resize handle uses modern browser pointer events instead. This removes the need for the overlay element and the raised stacking order, providing more reliable resizing across different integration environments and resolving the overlap with the floating sidebar.
144
+
53
145
54
146
[[additions]]
55
147
== Additions
@@ -89,6 +181,13 @@ The following premium plugin updates were released alongside {productname} {rele
89
181
90
182
{productname} {release-version} also includes the following bug fix<es>:
91
183
184
+
=== Indentation is now applied to all selected table cells
185
+
// #TINY-14370
186
+
187
+
Previously, applying indentation with multiple table cells selected affected only the cell where the pointer was released. The action used the browser's native selection rather than the editor's cell selection, so the remaining selected cells were left unchanged.
188
+
189
+
In {productname} {release-version}, indentation is applied to every cell in the selection.
190
+
92
191
// === <TINY-vwxyz 1 changelog entry>
93
192
// #TINY-vwxyz1
94
193
@@ -101,6 +200,27 @@ Previously, a context toolbar configured with `position: 'line'`, such as a quic
101
200
102
201
In {productname} {release-version}, a context toolbar that uses `position: 'line'` now flips to the opposite side when there is not enough space. The toolbar remains fully visible and usable in constrained layouts.
103
202
203
+
=== Some annotated text was hidden when printed even though it should have been visible
204
+
// #TINY-14296
205
+
206
+
Previously, text marked by annotation features, such as spelling indicators, could be hidden when a page was printed. The annotations were wrapped in internal placeholder elements that were hidden during printing, which also hid the text inside them.
207
+
208
+
In {productname} {release-version}, placeholder elements that act only as wrappers now hide their styling rather than their contents when printing. Annotation highlights remain hidden in the printed output, while the underlying text is printed as expected.
209
+
210
+
=== Worked around a Chromium bug where clicking on the right of an `li` could fail
211
+
// #TINY-13886
212
+
213
+
Previously, clicking to the right of the content in a list item could place the cursor at the start of the item instead of at the location that was clicked. This was caused by a Chromium browser bug that moved the caret to an incorrect position.
214
+
215
+
In {productname} {release-version}, a targeted workaround detects this case and corrects the caret position. Clicking to the right of a list item now places the cursor where expected.
216
+
217
+
=== Using the undo keyboard shortcut did not restore editor selection correctly
218
+
// #TINY-14255
219
+
220
+
Previously, pressing the undo keyboard shortcut (Ctrl+Z, or Cmd+Z on macOS) after deleting a selection could leave the cursor in the wrong position. An earlier change registered an extra undo step whenever Ctrl or Cmd was pressed, so the step was recorded before the deleted content was restored.
221
+
222
+
In {productname} {release-version}, {productname} registers that undo step only when Ctrl or Cmd is pressed together with Backspace or Delete, rather than on every Ctrl or Cmd key press. Undoing the deletion of a selection now restores both the content and the original selection correctly.
0 commit comments