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, April 02^nd^, 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, April 09^th^, 2025. These release notes provide an overview of the changes for {productname} {release-version}, including:
The following new Premium plugin was released alongside {productname} {release-version}.
35
-
36
-
=== <Premium plugin name>
37
-
38
-
The new Premium plugin, **<Premium plugin name>** // description here.
39
-
40
-
For information on the **<Premium plugin name>** plugin, see xref:<plugincode>.adoc[<Premium plugin name>].
41
-
42
-
43
-
[[new-open-source-plugin]]
44
-
== New Open Source plugin
45
-
46
-
The following new Open Source plugin was released alongside {productname} {release-version}.
47
-
48
-
=== <Open source plugin name>
49
-
50
-
The new open source plugin, **<Open source plugin name>** // description here.
51
-
52
-
For information on the **<Open source plugin name>** plugin, see xref:<plugincode>.adoc[<Open source plugin name>].
53
20
54
21
55
22
[[accompanying-premium-plugin-changes]]
@@ -78,6 +45,15 @@ The {productname} {release-version} release includes an accompanying release of
78
45
79
46
**Comments** includes the following fix, addition and change.
80
47
48
+
=== It wasn't possible to add comments to selected footnotes elements.
49
+
// #TINY-11842
50
+
51
+
In previous versions of {productname}, it was not possible to add comments to footnotes (created by the xref:footnotes.adoc[Footnotes] plugin) when selecting the footnote element.
52
+
53
+
As a result, attempting to add a comment would result in the comment being attached to a word outside the footnote as they were not considered valid block elements.
54
+
55
+
{productname} {release-version} addresses this issue. Comments can now be added directly to the entire footnote element, similar to how comments are handled for figures and other comparable elements.
56
+
81
57
=== A confirmation dialog now appears when resolving conversation to match the UX of deleting a conversation.
82
58
// #TINY-11324
83
59
@@ -97,54 +73,6 @@ In {productname} {release-version}, a new `+tinycomments_fetch_author_info+` cal
97
73
98
74
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
99
75
100
-
=== Math
101
-
102
-
The {productname} {release-version} release includes an accompanying release of the **Math** premium plugin.
103
-
104
-
**Math** includes the following addition.
105
-
106
-
==== New `extended_mathml_attributes` and `extended_mathml_elements` options.
107
-
// #TINY-11756
108
-
109
-
To improve flexibility when working with MathML content, especially in cases where new attributes or elements are not yet supported by DOMPurify, two new configuration options have been introduced: xref:math.adoc#extended-mathml-elements[extended_mathml_elements] and xref:math.adoc#extended-mathml-attributes[extended_mathml_attributes].
110
-
111
-
Prior to {release-version}, MathML elements and attributes were treated the same as all other content, with no special handling for MathML-specific structures. As a result, unsupported elements and attributes were either retained without validation or stripped without regard to their MathML context.
112
-
113
-
In {productname} {release-version}, MathML content is now filtered separately from general HTML using DOMPurify. As part of this change, support has been added to selectively allow specific elements and attributes *within* a `<math>` element using the new configuration options.
114
-
115
-
The new options allow users to define lists of MathML elements and attributes that should be preserved, even if DOMPurify does not currently recognize them. This enables quicker user-side updates in response to evolving MathML specifications without disabling sanitization or waiting for upstream changes.
116
-
117
-
* **`+extended_mathml_elements+`**: allows a list of additional MathML elements to be preserved.
118
-
* **`+extended_mathml_attributes+`**: allows a list of additional MathML attributes to be preserved.
119
-
120
-
These options apply only within MathML contexts and do not affect general HTML content. They enable use cases such as preserving `+<mn>+` elements and attributes like `linebreak` in MathML expressions.
121
-
122
-
.Example of MathML with preserved elements and attributes
123
-
[source,js]
124
-
----
125
-
tinymce.init({
126
-
selector: "textarea",
127
-
extended_mathml_elements: [ "mn" ],
128
-
extended_mathml_attributes: [ "linebreak" ]
129
-
});
130
-
----
131
-
132
-
.Example of MathML with preserved elements and attributes
133
-
[source,html]
134
-
----
135
-
<p>
136
-
<math xmlns="http://www.w3.org/1998/Math/MathML">
137
-
<mrow><mn>0.196</mn></mrow>
138
-
<mspace linebreak="newline"></mspace>
139
-
<mrow><mo>=</mo></mrow>
140
-
<mspace linebreak="newline"></mspace>
141
-
<mrow><mn>0.196</mn></mrow>
142
-
</math>
143
-
</p>
144
-
----
145
-
146
-
For information on the **Math** premium plugin, see: xref:math.adoc[Math].
147
-
148
76
=== Export to Word
149
77
150
78
The {productname} {release-version} release includes an accompanying update to the **Export to Word** premium plugin.
@@ -222,49 +150,31 @@ With the release of {productname} {release-version}, this issue has been resolve
222
150
223
151
For information on the **Image Optimizer (Powered by Uploadcare)** plugin, see xref:uploadcare.adoc[Image Optimizer (Powered by Uploadcare)].
The following Premium plugin has been announced as reaching its end-of-life:
229
-
230
-
=== <Premium plugin name eol>
231
-
232
-
{productname}’s xref:<plugincode>.adoc[<Premium plugin name eol>] plugin will be deactivated on <month> <DD>, <YYYY>, and is no longer available for purchase.
== Accompanying open source plugin end-of-life announcement
237
-
238
-
The following open source plugin has been announced as reaching its end-of-life:
239
-
240
-
=== <Open source plugin name eol>
241
153
242
-
{productname}’s xref:<plugincode>.adoc[<Open source plugin name eol>] plugin will be deactivated on <month> <DD>, <YYYY>, and is no longer available for purchase.
The {productname} {release-version} release includes an accompanying release of the **Enhanced Skins & Icon Packs**.
157
+
{productname} {release-version} also includes the following improvements:
249
158
250
-
=== Enhanced Skins & Icon Packs
159
+
=== The focus outline was misaligned with the comment card border after saving an edited comment.
160
+
// #TINY-11329
251
161
252
-
The **Enhanced Skins & Icon Packs** release includes the following updates:
162
+
In previous versions of {productname}, the keyboard focus styles were not properly aligned with the comment card during the process of saving an edited comment, resulting in a poor user interface.
253
163
254
-
The **Enhanced Skins & Icon Packs** were rebuilt to pull in the changes also incorporated into the default {productname} {release-version} skin, Oxide.
164
+
{productname} {release-version} addresses this by adjusting the focus styles, ensuring a more polished user interface while saving an edited comment.
255
165
256
-
For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-and-icon-packs.adoc[Enhanced Skins & Icon Packs].
166
+
=== The `+editor.selection.scrollIntoView()+` method now pads the target scroll area with a small margin, ensuring content doesn't sit at the very edge of the viewport.
167
+
// #TINY-11786
257
168
169
+
Previously, when cycling through accessibility issues in the a11y checker dialog, the highlighted content could appear aligned to the very edge of the viewport, making it difficult to identify and visually track. This behavior impacted usability by reducing the effectiveness of the a11y checker tool.
258
170
259
-
[[improvements]]
260
-
== Improvements
171
+
In {productname} {release-version}, the `+editor.selection.scrollIntoView()+` method was updated to include a top and bottom margin, aligning the highlighted content to a fixed `30px` from the edge of the viewport. Additionally, a visual overlay was introduced to draw attention to the selected element. These changes improve visibility, provide smoother and more intuitive scroll positioning, and enhance the overall user experience when navigating accessibility issues in {productname}.
261
172
262
-
{productname} {release-version} also includes the following improvement<s>:
263
173
264
-
=== <TINY-vwxyz 1 changelog entry>
265
-
// #TINY-vwxyz1
174
+
[[additions]]
175
+
== Additions
266
176
267
-
// CCFR here.
177
+
{productname} {release-version} also includes the following additions:
268
178
269
179
=== New subtoolbar support for context toolbars.
270
180
// #TINY-11748
@@ -307,58 +217,58 @@ tinymce.init({
307
217
308
218
For more information on context toolbars, see xref:contexttoolbar.adoc[Context toolbars].
309
219
310
-
=== The `+editor.selection.scrollIntoView()+` method now pads the target scroll area with a small margin, ensuring content doesn't sit at the very edge of the viewport.
311
-
// #TINY-11786
312
-
313
-
Previously, when cycling through accessibility issues in the a11y checker dialog, the highlighted content could appear aligned to the very edge of the viewport, making it difficult to identify and visually track. This behavior impacted usability by reducing the effectiveness of the a11y checker tool.
314
-
315
-
In {productname} {release-version}, the `+editor.selection.scrollIntoView()+` method was updated to include a top and bottom margin, aligning the highlighted content to a fixed `30px` from the edge of the viewport. Additionally, a visual overlay was introduced to draw attention to the selected element. These changes improve visibility, provide smoother and more intuitive scroll positioning, and enhance the overall user experience when navigating accessibility issues in {productname}.
316
-
317
-
318
-
[[additions]]
319
-
== Additions
320
-
321
-
{productname} {release-version} also includes the following addition<s>:
322
-
323
-
=== <TINY-vwxyz 1 changelog entry>
324
-
// #TINY-vwxyz1
220
+
=== New `extended_mathml_attributes` and `extended_mathml_elements` options.
221
+
// #TINY-11756
325
222
326
-
// CCFR here.
223
+
To improve flexibility when working with MathML content, especially in cases where new attributes or elements are not yet supported by DOMPurify, two new configuration options have been introduced: xref:math.adoc#extended-mathml-elements[extended_mathml_elements] and xref:math.adoc#extended-mathml-attributes[extended_mathml_attributes].
327
224
225
+
Prior to {release-version}, MathML elements and attributes were treated the same as all other content, with no special handling for MathML-specific structures. As a result, unsupported elements and attributes were either retained without validation or stripped without regard to their MathML context.
328
226
329
-
[[changes]]
330
-
== Changes
227
+
In {productname} {release-version}, MathML content is now filtered separately from general HTML using DOMPurify. As part of this change, support has been added to selectively allow specific elements and attributes *within* a `<math>` element using the new configuration options.
331
228
332
-
{productname} {release-version} also includes the following change<s>:
229
+
The new options allow users to define lists of MathML elements and attributes that should be preserved, even if DOMPurify does not currently recognize them. This enables quicker user-side updates in response to evolving MathML specifications without disabling sanitization or waiting for upstream changes.
333
230
334
-
=== <TINY-vwxyz 1 changelog entry>
335
-
// #TINY-vwxyz1
231
+
* **`+extended_mathml_elements+`**: allows a list of additional MathML elements to be preserved.
232
+
* **`+extended_mathml_attributes+`**: allows a list of additional MathML attributes to be preserved.
336
233
337
-
// CCFR here.
234
+
These options apply only within MathML contexts and do not affect general HTML content. They enable use cases such as preserving `+<mn>+` elements and attributes like `linebreak` in MathML expressions.
338
235
236
+
.Example of MathML with preserved elements and attributes
237
+
[source,js]
238
+
----
239
+
tinymce.init({
240
+
selector: "textarea",
241
+
extended_mathml_elements: [ "mn" ],
242
+
extended_mathml_attributes: [ "linebreak" ]
243
+
});
244
+
----
339
245
340
-
[[removed]]
341
-
== Removed
246
+
.Example of MathML with preserved elements and attributes
247
+
[source,html]
248
+
----
249
+
<p>
250
+
<math xmlns="http://www.w3.org/1998/Math/MathML">
251
+
<mrow><mn>0.196</mn></mrow>
252
+
<mspace linebreak="newline"></mspace>
253
+
<mrow><mo>=</mo></mrow>
254
+
<mspace linebreak="newline"></mspace>
255
+
<mrow><mn>0.196</mn></mrow>
256
+
</math>
257
+
</p>
258
+
----
342
259
343
-
{productname} {release-version} also includes the following removal<s>:
260
+
=== New `onboarding` option
261
+
// #TINY-11931
344
262
345
-
=== <TINY-vwxyz 1 changelog entry>
346
-
// #TINY-vwxyz1
263
+
{productname} {release-version} introduces a new `+onboarding+` option to enhance the developer experience during the 14-day trial period. This option controls the display of a cloud promotion banner highlighting paid features available during the trial. The banner is automatically hidden when the trial ends or when the editor is correctly configured, ensuring a smoother and less intrusive setup experience.
347
264
348
-
// CCFR here.
265
+
For more information, see xref:promotions.adoc#onboarding[onboarding].
349
266
350
267
351
268
[[bug-fixes]]
352
269
== Bug fixes
353
270
354
-
{productname} {release-version} also includes the following bug fix<es>:
355
-
356
-
=== The focus outline was misaligned with the comment card border after saving an edited comment.
357
-
// #TINY-11329
358
-
359
-
In previous versions of {productname}, the keyboard focus styles were not properly aligned with the comment card during the process of saving an edited comment, resulting in a poor user interface.
360
-
361
-
{productname} {release-version} addresses this by adjusting the focus styles, ensuring a more polished user interface while saving an edited comment.
271
+
{productname} {release-version} also includes the following bug fixes:
362
272
363
273
=== Setting editor height to a `pt` or `em` value was ignoring min/max height settings.
364
274
// #TINY-11108
@@ -368,47 +278,4 @@ Previously, when the editor height was set using relative units such as `pt` or
368
278
=== The tooltip for the `blockquote` button was not translated in Hebrew.
369
279
// #TINY-11732
370
280
371
-
Previously, the tooltip for the `blockquote` button was not translated in Hebrew. {productname} {release-version} addresses this by adding a new Hebrew translation to the tooltip for the `blockquote` button.
372
-
373
-
=== It wasn't possible to add comments to selected footnotes elements.
374
-
// #TINY-11842
375
-
376
-
In previous versions of {productname}, it was not possible to add comments to footnotes (created by the xref:footnotes.adoc[Footnotes] plugin) when selecting the footnote element.
377
-
378
-
As a result, attempting to add a comment would result in the comment being attached to a word outside the footnote as they were not considered valid block elements.
379
-
380
-
{productname} {release-version} addresses this issue. Comments can now be added directly to the entire footnote element, similar to how comments are handled for figures and other comparable elements.
381
-
382
-
383
-
[[security-fixes]]
384
-
== Security fixes
385
-
386
-
{productname} {release-version} includes <a fix | fixes for the following security issue<s>:
387
-
388
-
=== <TINY-vwxyz 1 changelog entry>
389
-
// #TINY-vwxyz1
390
-
391
-
// CCFR here.
392
-
393
-
394
-
[[deprecated]]
395
-
== Deprecated
396
-
397
-
{productname} {release-version} includes the following deprecation<s>:
398
-
399
-
=== The `<plugin>` configuration property, `<name>`, has been deprecated
400
-
401
-
// placeholder here.
402
-
403
-
404
-
[[known-issues]]
405
-
== Known issues
406
-
407
-
This section describes issues that users of {productname} {release-version} may encounter and possible workarounds for these issues.
408
-
409
-
There <is one | are <number> known issue<s> in {productname} {release-version}.
410
-
411
-
=== <TINY-vwxyz 1 changelog entry>
412
-
// #TINY-vwxyz1
413
-
414
-
// CCFR here.
281
+
Previously, the tooltip for the `blockquote` button was not translated in Hebrew. {productname} {release-version} addresses this by adding a new Hebrew translation to the tooltip for the `blockquote` button.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/changelog.adoc
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,6 @@ NOTE: This is the {productname} Community version changelog. For information abo
15
15
// #TINY-11931
16
16
17
17
=== Improved
18
-
* Dialog menu dropdowns now close when a dialog is moved.
19
-
// #TINY-11368
20
18
* Focus outline was misaligned with comment card border on saving an edit.
21
19
// #TINY-11329
22
20
* The `editor.selection.scrollIntoView()` method now pads the target scroll area with a small margin, ensuring content doesn't sit at the very edge of the viewport.
@@ -29,14 +27,6 @@ NOTE: This is the {productname} Community version changelog. For information abo
29
27
=== Fixed
30
28
* Setting editor height to a `pt` or `em` value was ignoring min/max height settings.
31
29
// #TINY-11108
32
-
* Exception when pressing tab in the last cell of a non-editable table.
33
-
// #TINY-11797
34
-
* Exception was thrown when trying to use context form API after component was detached.
35
-
// #TINY-11781
36
-
* Deleting an empty block within <li> would move cursor at the end of the <li>.
37
-
// #TINY-11763
38
-
* Deleting an empty block that is between two lists would throw an error when all of the elements were nested inside the same <li>.
0 commit comments