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}.
26
26
27
+
=== Export to PDF
28
+
29
+
The {productname} {release-version} release includes an accompanying release of the **Export to PDF** premium plugin.
30
+
31
+
**Export to PDF** Premium plugin includes the following improvement.
32
+
33
+
==== The `format` property in `exportpdf_converter_options` now accepts lowercase
34
+
// #TINY-11722
35
+
36
+
Previously, the `format` property in `exportpdf_converter_options` only accepted case-sensitive uppercase values, which lead to inconsistencies when generating PDF exports. This improvement ensures that lowercase values are now correctly recognized, making configuration more flexible and reducing potential formatting errors.
37
+
38
+
For information on the **Export to PDF** plugin, see: xref:exportpdf.adoc[Export to PDF].
39
+
27
40
=== Export to Word
28
41
29
42
The {productname} {release-version} release includes an accompanying release of the **Export to Word** premium plugin.
@@ -59,6 +72,13 @@ The {productname} {release-version} release includes an accompanying release of
59
72
60
73
**Comments** includes the following fixes.
61
74
75
+
==== Editing a comment and adding a mention to the comment would result in the mention not showing correctly after saving the comment.
76
+
// #TINY-11602
77
+
78
+
Previously, in the **Comments** premium plugin, an issue was identified where mentions were not displayed correctly when editing a comment, adding a mention, and then saving the comment.
79
+
80
+
{productname} {release-version} resolves this issue by ensuring that newly added mentions to an existing comment are displayed correctly.
81
+
62
82
==== Pressing Keyboard shorctut `cmd+alt+m` when cursor is on annotated content now opens and focuses the reply textarea.
63
83
// #TINY-11321
64
84
@@ -74,6 +94,27 @@ In previous versions of **Comments**, the side panel header blended into the bod
74
94
75
95
{productname} {release-version} improves this by enhancing the side panel header’s visibility, creating a clearer distinction from the body, and refining the overall UI aesthetics.
76
96
97
+
==== Editor now dispatches `Change` event after a comment is edited or a reply is created.
98
+
// #TINY-11802
99
+
100
+
Previously, when a comment was edited or replied to, the editor did not enter a dirty state. As a result, in embedded mode with the xref:save.adoc[Save] plugin, the save button remained disabled after replying to or editing a comment, which was not the expected behavior.
101
+
102
+
In {productname} {release-version}, this issue has been addressed. The editor now transitions to a dirty state when a comment is edited or replied to, ensuring that changes can be saved using the save button as intended.
103
+
104
+
==== Comment card jumps when editing a large comment in Chrome
105
+
// #TINY-11729
106
+
107
+
Previously, when editing a comment larger than the height of the comments sidebar, the sidebar would briefly jump before returning to its intended position. This caused visual disruptions that impacted the editing experience.
108
+
109
+
{productname} {release-version} resolves this issue by ensuring the comment sidebar remains stable, preventing unintended jumps when editing large comments.
110
+
111
+
==== Closing the comment kebab menu with keyboard would result in the editor dispatching a `blur` event.
112
+
// #TINY-11172
113
+
114
+
In previous versions of **Comments**, an issue was identified where the editor would trigger a `blur` event if the comment kebab menu was closed using the `escape` key. This occurred even when the editor still had focus, leading to confusing behavior.
115
+
116
+
{productname} {release-version} resolves this issue by ensuring that focus is properly managed when closing the kebab menu, rather than relying on the browser. This ensures that the editor does not trigger any `blur` events.
117
+
77
118
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].
78
119
79
120
=== Image Optimizer
@@ -107,18 +148,30 @@ This caused confusion in identifying the problem during setup.
107
148
108
149
{productname} {release-version} addresses this by providing a more detailed error message when the `uploadcare_public_key` is not configured.
109
150
151
+
==== Toolbar text field was not properly rendering focus.
152
+
// #TINY-11658
153
+
154
+
Previously, input elements lacked styling logic to display a border when focused, resulting in no visible indication of focus.
155
+
This issue has been resolved in {productname} {release-version}. Input elements now correctly display a border when focused, ensuring improved visual feedback.
156
+
157
+
==== It was possible to `tab` to a toolbar group that had all children disabled.
158
+
// #TINY-11665
159
+
160
+
Previously in the **Image Optimizer** premium plugin, a fallback mechanism caused focus to shift to the nearest ancestor element. As a result, if focus was applied to a disabled input, its container would receive the focus.
161
+
162
+
{productname} {release-version} resolves this issue by ensuring that containers with only disabled elements are no longer focusable, preventing unintended focus behavior.
163
+
110
164
For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
111
165
112
166
[[improvements]]
113
167
== Improvements
114
168
115
169
{productname} {release-version} also includes the following improvement<s>:
116
170
117
-
=== <TINY-vwxyz 1 changelog entry>
118
-
// #TINY-vwxyz1
119
-
120
-
// CCFR here.
171
+
=== Added `link_attributes_postprocess` option that allows overriding attributes of a link inserted through the link dialog.
172
+
// #TINY-11707
121
173
174
+
Previously in the xref:link.adoc[Link] plugin, there was no ability to override attributes of a link. With the release of {productname} {release-version}, a new option xref:link.adoc#link_attributes_postprocess[link_attributes_postprocess] has been added that allows this functionality.
122
175
123
176
[[additions]]
124
177
== Additions
@@ -162,6 +215,13 @@ the help dialog would not open if the plugin was disabled, leading to confusion.
162
215
163
216
{productname} {release-version} addresses this issue by ensuring that if the help plugin is disabled, the screen reader announces only "Rich Text Area." If the help plugin is enabled, the screen reader announces "Rich Text Area. Press `ALT-0` for help.".
164
217
218
+
=== The `semantics` element in MathML was not properly preserved when `annotation` elements were allowed.
219
+
// #TINY-11755
220
+
221
+
Previously, in {productname}, an issue was identified in which the `semantics` MathML element was removed, even when a specific annotation element was allowed by the `allow_mathml_annotation_encodings` property. As a result, the generated MathML was invalid because the annotation element must be a child of a `semantics` element. This also caused rendering issues in some browsers.
222
+
223
+
In {productname} {release-version}, this issue has been resolved by preserving the `semantics` element whenever the `allow_mathml_annotation_encodings` property is set to a non-empty array. This ensures that valid MathML is generated, improving compatibility with third-party tools and browser rendering.
224
+
165
225
=== Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips
166
226
// #TINY-11768
167
227
@@ -176,6 +236,13 @@ Previously, an issue occurred where toggling a caption on a floating image did n
176
236
177
237
In {productname} {release-version}, this issue has been resolved by ensuring that the float property is removed when toggling the caption. As a result, the image and caption text now align correctly.
178
238
239
+
=== Fixed keyboard navigation for size inputs in context forms.
240
+
// #TINY-11394
241
+
242
+
Previously, input and slider elements in the context toolbar did not support keyboard navigation, preventing users from accessing and adjusting these elements via the keyboard.
243
+
244
+
With the release of {productname} {release-version}, keyboard navigation has been implemented for these elements, ensuring seamless accessibility and improved usability.
0 commit comments