Skip to content

Commit 75ac1d5

Browse files
kemister85kemister85
authored
Merge branch 'feature/7.8.0/DOC-3131' into feature/7.8.0/DOC-3131_DOC-3161
2 parents e2176f2 + 9776675 commit 75ac1d5

File tree

5 files changed

+224
-11
lines changed

5 files changed

+224
-11
lines changed

‎modules/ROOT/pages/7.8.0-release-notes.adoc‎

Lines changed: 108 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -57,23 +57,38 @@ For information on the **<Open source plugin name>** plugin, see xref:<plugincod
5757

5858
The following premium plugin updates were released alongside {productname} {release-version}.
5959

60-
=== <Premium plugin name 1> <Premium plugin name 1 version>
60+
=== Enhanced Code Editor
6161

62-
The {productname} {release-version} release includes an accompanying release of the **<Premium plugin name 1>** premium plugin.
62+
The {productname} {release-version} release includes an accompanying release of the **Enhanced Code Editor** premium plugin.
6363

64-
**<Premium plugin name 1>** <Premium plugin name 1 version> includes the following <fixes, changes, improvements>.
64+
**Enhanced Code Editor includes the following fix**.
6565

66-
==== <Premium plugin name 1 change 1>
66+
==== Source Code editor was not scrolling to the editor's caret position in Firefox.
67+
// #TINY-11811
6768

68-
// CCFR here.
69+
Previously, an issue was identified where the Enhanced Code Editor in Firefox did not automatically scroll to the caret's relative position within the editor. As a result, users were required to manually scroll to locate the corresponding element, leading to a suboptimal user experience.
70+
71+
With the release of {productname} {release-version}, this issue has been resolved. The Enhanced Code Editor in Firefox now exhibits consistent behavior with other browsers, automatically scrolling to the caret's position when the editor is opened. This enhancement significantly improves the user experience by eliminating the need for manual navigation.
6972

70-
For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
73+
For information on the **Enhanced Code Editor** plugin, see: xref:advcode.adoc[Enhanced Code Editor].
7174

7275
=== Comments
7376

7477
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
7578

76-
**Comments** includes the following addition.
79+
**Comments** includes the following fix, addition and change.
80+
81+
=== A confirmation dialog now appears when resolving conversation to match the UX of deleting a conversation.
82+
// #TINY-11324
83+
84+
Previously, resolving a conversation did not trigger a confirmation dialog, unlike the behavior when deleting a conversation. Selecting *Resolve conversation* from the conversation kebab menu would immediately perform the action without user confirmation.
85+
86+
{productname} {release-version} introduces a confirmation dialog for resolving conversations, ensuring a consistent user experience and helping prevent unintentional resolutions.
87+
88+
=== The `change` event was not dispatched when deleting a comment reply.
89+
// #TINY-11830
90+
91+
Previously, deleting a comment reply did not dispatch a `change` event, which prevented the {productname} Save plugin from detecting the editor as modified. As a result, the “Save” button remained disabled after deleting a reply, potentially leading to lost changes. This issue has been resolved in {release-version}. Deleting a comment reply now correctly triggers a dirty state, ensuring the Save plugin enables the “Save” button as expected.
7792

7893
=== New `tinycomments_fetch_author_info` option that allows integrators to specify the current author info in callback mode.
7994
// #TINY-11680
@@ -82,6 +97,75 @@ In {productname} {release-version}, a new `+tinycomments_fetch_author_info+` cal
8297

8398
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
8499

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+
=== Export to Word
149+
150+
The {productname} {release-version} release includes an accompanying update to the **Export to Word** premium plugin.
151+
152+
==== Improved handling of relative URLs using `base_url` configuration for Export to Word
153+
// #TINY-11923
154+
155+
Previously, the `exportword` plugin converted relative URLs (e.g., `+/relative/url+`) into incorrect absolute URLs during export, causing hyperlinks in Word documents to direct users to unintended or non-existent destinations. This issue has been resolved. The plugin now correctly resolves relative URLs using the `base_url` configuration option, ensuring exported Word documents contain valid and functional hyperlinks.
156+
157+
For more information, see: xref:exportword.adoc[Export to Word].
158+
159+
=== Export to PDF
160+
161+
The {productname} {release-version} release includes an accompanying update to the **Export to PDF** premium plugin.
162+
163+
==== Improved handling of relative URLs using `base_url` configuration for Export to PDF
164+
// #TINY-11923
165+
166+
The `exportpdf` plugin previously transformed relative URLs (e.g., `+/relative/url+`) into incorrect absolute URLs, resulting in broken or misdirected links in exported PDF documents. This issue has been addressed. The plugin now uses the `base_url` configuration option to correctly resolve relative URLs, ensuring that links in exported PDFs lead to the correct destinations.
167+
168+
For more information, see: xref:exportpdf.adoc[Export to PDF].
85169

86170
[[accompanying-premium-plugin-end-of-life-announcement]]
87171
== Accompanying Premium plugin end-of-life announcement
@@ -127,6 +211,13 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
127211

128212
// CCFR here.
129213

214+
=== 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.
215+
// #TINY-11786
216+
217+
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.
218+
219+
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}.
220+
130221

131222
[[additions]]
132223
== Additions
@@ -166,10 +257,17 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
166257

167258
{productname} {release-version} also includes the following bug fix<es>:
168259

169-
=== <TINY-vwxyz 1 changelog entry>
170-
// #TINY-vwxyz1
260+
=== The focus outline was misaligned with the comment card border after saving an edited comment.
261+
// #TINY-11329
171262

172-
// CCFR here.
263+
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.
264+
265+
{productname} {release-version} addresses this by adjusting the focus styles, ensuring a more polished user interface while saving an edited comment.
266+
267+
=== Setting editor height to a `pt` or `em` value was ignoring min/max height settings.
268+
// #TINY-11108
269+
270+
Previously, when the editor height was set using relative units such as `pt` or `em`, the editor was unable to parse and evaluate these values correctly. As a result, it would bypass the `min_height` and `max_height` checks, leading to unpredictable layout behavior. This issue was especially noticeable during initialization, although resizing later used the browser-calculated content box height, which partially masked the problem. In {release-version}, {productname} now attempts to compute height values from additional unit types to better enforce minimum and maximum height constraints. Some units, such as percentages (`%`), may still override explicit height values due to browser limitations in determining the final rendered size. This update ensures that `min_height` and `max_height` settings are more reliably applied across a wider range of unit types.
173271

174272

175273
[[security-fixes]]

‎modules/ROOT/pages/math.adoc‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,12 @@ include::partial$misc/plugin-toolbar-button-id-boilerplate.adoc[]
7272

7373
include::partial$misc/plugin-menu-item-id-boilerplate.adoc[]
7474

75+
== Options
76+
77+
include::partial$configuration/extended_mathml_elements.adoc[leveloffset=+1]
78+
79+
include::partial$configuration/extended_mathml_attributes.adoc[leveloffset=+1]
80+
7581
== Commands
7682

7783
The {pluginname} plugin provides the following {productname} commands.

‎modules/ROOT/partials/configuration/extended_mathml_attributes.adoc‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
[[extended-mathml-attributes]]
2+
== `+extended_mathml_attributes+`
3+
4+
This option allows a specific list of additional MathML attributes to be preserved in the editor content, even if they are not included in the default DOMPurify allowlist. This setting only affects attributes used within MathML markup and has no effect on general HTML content.
5+
6+
*Type:* `+Array+` of `+Strings+`
7+
8+
*Default value:* `+[]+` (empty array)
9+
10+
=== Example: using `+extended_mathml_attributes+`
11+
12+
[source,js]
13+
----
14+
tinymce.init({
15+
selector: 'textarea',
16+
extended_mathml_attributes: [ 'linebreak', 'encoding' ]
17+
});
18+
----
19+
20+
.Example of MathML with preserved attributes
21+
[source,html]
22+
----
23+
<p>
24+
<math xmlns="http://www.w3.org/1998/Math/MathML">
25+
<mrow linebreak="newline" encoding="utf8">
26+
<mi>x</mi>
27+
<mo>=</mo>
28+
<mfrac>
29+
<mrow>
30+
<mo>&#x2212;</mo>
31+
<mi>b</mi>
32+
<mo>&#x00B1;</mo>
33+
<msqrt>
34+
<mrow>
35+
<msup>
36+
<mi>b</mi>
37+
<mn>2</mn>
38+
</msup>
39+
<mo>&#x2212;</mo>
40+
<mn>4</mn>
41+
<mo>&#x2062;</mo>
42+
<mi>a</mi>
43+
<mo>&#x2062;</mo>
44+
<mi>c</mi>
45+
</mrow>
46+
</msqrt>
47+
</mrow>
48+
<mrow>
49+
<mn>2</mn>
50+
<mo>&#x2062;</mo>
51+
<mi>a</mi>
52+
</mrow>
53+
</mfrac>
54+
</mrow>
55+
</math>
56+
</p>
57+
----

‎modules/ROOT/partials/configuration/extended_mathml_elements.adoc‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
[[extended-mathml-elements]]
2+
== `+extended_mathml_elements+`
3+
4+
This option allows a specific list of additional MathML elements to be preserved in the editor content, even if they are not included in the default DOMPurify allowlist. This setting only affects elements used within MathML markup and has no effect on general HTML content.
5+
6+
*Type:* `+Array+` of `+Strings+`
7+
8+
*Default value:* `+[]+` (empty array)
9+
10+
=== Example: using `+extended_mathml_elements+`
11+
12+
[source,js]
13+
----
14+
tinymce.init({
15+
selector: 'textarea',
16+
extended_mathml_elements: [ 'mn', 'mspace' ]
17+
});
18+
----
19+
20+
.Example of MathML with preserved elements
21+
[source,html]
22+
----
23+
<p>
24+
<math xmlns="http://www.w3.org/1998/Math/MathML">
25+
<mrow>
26+
<mi>a</mi>
27+
<mo>=</mo>
28+
<mfrac>
29+
<mrow>
30+
<mn>1</mn>
31+
<mo>+</mo>
32+
<mn>√2</mn>
33+
</mrow>
34+
<mn>3</mn>
35+
</mfrac>
36+
<mspace width="1em"></mspace>
37+
<mo>&#x222A;</mo>
38+
<mspace width="1em"></mspace>
39+
<msup>
40+
<mn>5</mn>
41+
<mn>2</mn>
42+
</msup>
43+
</mrow>
44+
</math>
45+
</p>
46+
----

‎modules/ROOT/partials/configuration/height.adoc‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,13 @@
33

44
`+height+` sets the height of the entire editor, including the menu bar, toolbars, and status bar.
55

6-
NOTE: If a number is provided, {productname} sets the height in pixels. If a string is provided, {productname} assumes the value is valid CSS and sets the editor's height as the string value. This allows for alternate units such as `+%+`, `+em+`, and `+vh+`.
6+
[NOTE]
7+
====
8+
* If a number is provided, {productname} sets the height in pixels by defult.
9+
* If a string is provided, {productname} assumes the value is valid CSS and sets the editor's height as the string value such as `+300px+`, `+50pt+`, or `+10em+`.
10+
11+
Note: that values such as `+100%+`, `+10vh+` and `auto` are not currently supported.
12+
====
713

814
*Type:* `+Number+` or `+String+`
915

0 commit comments

Comments
 (0)