Skip to content

Commit f411af7

Browse files
abhinavgandhamabhinavgandham
committed
DOC-3132: Adjusted layout of entries to fit changelog.
1 parent 8d6d9d9 commit f411af7

File tree

1 file changed

+88
-86
lines changed

1 file changed

+88
-86
lines changed

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

Lines changed: 88 additions & 86 deletions
Original file line numberDiff line numberDiff line change
@@ -59,48 +59,6 @@ include::partial$misc/admon-no-functionality-changes-in-updated-server-side-comp
5959

6060
The following premium plugin updates were released alongside {productname} {release-version}.
6161

62-
=== Export to PDF
63-
64-
The {productname} {release-version} release includes an accompanying release of the **Export to PDF** premium plugin.
65-
66-
**Export to PDF** Premium plugin includes the following improvement.
67-
68-
==== The `format` property in `exportpdf_converter_options` now accepts lowercase
69-
// #TINY-11722
70-
71-
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.
72-
73-
For information on the **Export to PDF** plugin, see: xref:exportpdf.adoc[Export to PDF].
74-
75-
=== Export to Word
76-
77-
The {productname} {release-version} release includes an accompanying release of the **Export to Word** premium plugin.
78-
79-
**Export to Word** includes the following fix.
80-
81-
==== A document watermark can now be specified for the exported file
82-
83-
Previously, the **Export to Word** premium plugin did not support watermarks, preventing integrators from adding them to exported Word documents.
84-
85-
With the release of {productname} {release-version} watermark functionality has been introduced, enabling watermarks to be included in exported documents.
86-
87-
For information on the **Export to Word** plugin, see: xref:exportword.adoc[Export to Word].
88-
89-
=== Advanced Typography
90-
91-
The {productname} {release-version} release includes an accompanying release of the **Advanced Typography** premium plugin.
92-
93-
**Advanced Typography** includes the following fix.
94-
95-
==== Serbian and Ukrainian languages were spelled incorrectly.
96-
// #TINY-11713
97-
98-
Previously, an issue was identified where `Ukrainian` and `Serbian` were incorrectly spelt in the typography plugin.
99-
100-
{productname} {release-version} addresses this by fixing the spelling.
101-
102-
For information on the **Advanced Typography** plugin, see: xref:advanced-typography.adoc[Advanced Typography].
103-
10462
=== Comments
10563

10664
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
@@ -150,13 +108,6 @@ In previous versions of **Comments**, an issue was identified where the editor w
150108

151109
{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.
152110

153-
==== Improved visual indication of keyboard focus for a comment annotation when there is an image inside.
154-
// #TINY-11596
155-
156-
In previous versions of **Comments**, annotated non-text elements occasionally displayed a double bottom border when selected, leading to a visual inconsistency that appeared buggy and clashed with existing border styles.
157-
158-
With the release of {productname} {release-version}, dedicated styles for selected non-text element annotations have been introduced. This enhancement improves the visual clarity of comment annotations on non-text elements such as images and videos.
159-
160111
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].
161112

162113
=== Image Optimizer
@@ -190,20 +141,49 @@ This caused confusion in identifying the problem during setup.
190141

191142
{productname} {release-version} addresses this by providing a more detailed error message when the `uploadcare_public_key` is not configured.
192143

193-
==== Toolbar text field was not properly rendering focus.
194-
// #TINY-11658
144+
For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
195145

196-
Previously, input elements lacked styling logic to display a border when focused, resulting in no visible indication of focus.
197-
This issue has been resolved in {productname} {release-version}. Input elements now correctly display a border when focused, ensuring improved visual feedback.
146+
=== Export to PDF
198147

199-
==== It was possible to `tab` to a toolbar group that had all children disabled.
200-
// #TINY-11665
148+
The {productname} {release-version} release includes an accompanying release of the **Export to PDF** premium plugin.
201149

202-
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.
150+
**Export to PDF** Premium plugin includes the following improvement.
203151

204-
{productname} {release-version} resolves this issue by ensuring that containers with only disabled elements are no longer focusable, preventing unintended focus behavior.
152+
==== The `format` property in `exportpdf_converter_options` now accepts lowercase
153+
// #TINY-11722
205154

206-
For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
155+
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.
156+
157+
For information on the **Export to PDF** plugin, see: xref:exportpdf.adoc[Export to PDF].
158+
159+
=== Export to Word
160+
161+
The {productname} {release-version} release includes an accompanying release of the **Export to Word** premium plugin.
162+
163+
**Export to Word** includes the following fix.
164+
165+
==== A document watermark can now be specified for the exported file
166+
167+
Previously, the **Export to Word** premium plugin did not support watermarks, preventing integrators from adding them to exported Word documents.
168+
169+
With the release of {productname} {release-version} watermark functionality has been introduced, enabling watermarks to be included in exported documents.
170+
171+
For information on the **Export to Word** plugin, see: xref:exportword.adoc[Export to Word].
172+
173+
=== Advanced Typography
174+
175+
The {productname} {release-version} release includes an accompanying release of the **Advanced Typography** premium plugin.
176+
177+
**Advanced Typography** includes the following fix.
178+
179+
==== Serbian and Ukrainian languages were spelled incorrectly.
180+
// #TINY-11713
181+
182+
Previously, an issue was identified where `Ukrainian` and `Serbian` were incorrectly spelt in the typography plugin.
183+
184+
{productname} {release-version} addresses this by fixing the spelling.
185+
186+
For information on the **Advanced Typography** plugin, see: xref:advanced-typography.adoc[Advanced Typography].
207187

208188
=== Enhanced Code Editor
209189

@@ -255,6 +235,13 @@ For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.a
255235

256236
{productname} {release-version} also includes the following improvements:
257237

238+
==== Improved visual indication of keyboard focus for a comment annotation when there is an image inside.
239+
// #TINY-11596
240+
241+
In previous versions of **Comments**, annotated non-text elements occasionally displayed a double bottom border when selected, leading to a visual inconsistency that appeared buggy and clashed with existing border styles.
242+
243+
With the release of {productname} {release-version}, dedicated styles for selected non-text element annotations have been introduced. This enhancement improves the visual clarity of comment annotations on non-text elements such as images and videos.
244+
258245
=== Not specifying a notification type (or specifying an incorrect one) now defaults to 'info'.
259246
// #TINY-11661
260247

@@ -280,12 +267,14 @@ Previously in the xref:link.adoc[Link] plugin, there was no ability to override
280267
[[bug-fixes]]
281268
== Bug fixes
282269

283-
{productname} <x.y[.z]> also includes the following bug fixes:
270+
{productname} {release-version} also includes the following bug fixes:
284271

285-
=== Dialog menu dropdowns now close when scrolling the editor container.
286-
// #TINY-11398
272+
=== Fixed keyboard navigation for size inputs in context forms.
273+
// #TINY-11394
287274

288-
Previously, dialog menu dropdowns were not positioned correctly after scrolling the editor container, causing them to remain visible even when the editor was no longer in view. This resulted in dropdowns being displayed without their corresponding dialog context. {productname} {release-version} updates the behavior to ensure that dialog menu dropdowns close on the window scroll event, preventing them from appearing out of context.
275+
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.
276+
277+
With the release of {productname} {release-version}, keyboard navigation has been implemented for these elements, ensuring seamless accessibility and improved usability.
289278

290279
=== The `insertContent` API was not replacing selected non-editable elements correctly.
291280
// #TINY-11714
@@ -295,6 +284,14 @@ As a result, integrators were unable to insert content into inline non-editable
295284

296285
{productname} {release-version} resolves this by modifying the functionality of the `insertContent` API to support this scenario. This ensures that integrators can now insert content into inline elements, making the `insertContent` API more robust.
297286

287+
=== Iframe aria text used to suggest to open help dialog even when the help plugin was not enabled.
288+
// #TINY-11672
289+
290+
Previously, an issue was identified where the aria-label attribute in the body element was set to “Rich Text Area. Press `ALT-0` for help”. This affected accessibility because the screen reader would announce this message, but when users pressed `ALT-0`,
291+
the help dialog would not open if the plugin was disabled, leading to confusion.
292+
293+
{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.".
294+
298295
=== Preview Dialog incorrectly opened anchor links in a new tab.
299296
// #TINY-11740
300297

@@ -305,13 +302,12 @@ This resulted in a poor user experience as users could not engage with anchor li
305302

306303
{productname} {release-version} resolves this issue by first checking whether a link is an anchor link and ensuring that users are navigated to the corresponding anchor element, which is the expected behavior.
307304

308-
=== Iframe aria text used to suggest to open help dialog even when the help plugin was not enabled.
309-
// #TINY-11672
305+
=== The `float` property was not properly removed from the image when converting an image into a captioned image.
306+
// #TINY-11670
310307

311-
Previously, an issue was identified where the aria-label attribute in the body element was set to “Rich Text Area. Press `ALT-0` for help”. This affected accessibility because the screen reader would announce this message, but when users pressed `ALT-0`,
312-
the help dialog would not open if the plugin was disabled, leading to confusion.
308+
Previously, an issue occurred where toggling a caption on a floating image did not remove the float property from the image, causing the caption text to be incorrectly positioned.
313309

314-
{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.".
310+
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.
315311

316312
=== The `semantics` element in MathML was not properly preserved when `annotation` elements were allowed.
317313
// #TINY-11755
@@ -320,19 +316,12 @@ Previously, in {productname}, an issue was identified in which the `semantics` M
320316

321317
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.
322318

323-
=== Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips
324-
// #TINY-11768
325-
326-
In previous versions of {productname}, hovering over toolbar menu item would display both a custom tooltip and the default browser tooltip. This caused confusing behavior, as the custom tooltip was difficult to read due to the browser tooltip overlapping it.
327-
328-
{productname} {release-version} resolves this issue by replacing the `title` attribute with the `aria-label` attribute for toolbar groupings, preventing the default browser tooltip from appearing.
329-
330-
=== Expanding selection to a word didn't work inside inline editing host elements.
331-
// #TINY-11304
319+
=== It was possible to `tab` to a toolbar group that had all children disabled.
320+
// #TINY-11665
332321

333-
Previously, an issue occurred where the selection did not expand as expected when using the `editor.selection.expand({ type: 'word' })` API when the selection was within an inline edit host element inside a non-editable parent.
322+
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.
334323

335-
This has been resolved in {productname} {release-version}, ensuring that the expanded selection now remains within the boundaries of the editable host element.
324+
{productname} {release-version} resolves this issue by ensuring that containers with only disabled elements are no longer focusable, preventing unintended focus behavior.
336325

337326
=== Keyboard navigation would get stuck on the 'more' toolbar button.
338327
// #TINY-11762
@@ -341,19 +330,32 @@ Previously, an issue was identified where keyboard navigation using the Tab key
341330

342331
In {productname} {release-version}, this issue has been resolved by implementing more precise filtering of viable tab targets. As a result, keyboard navigation now functions smoothly without getting stuck.
343332

344-
=== The `float` property was not properly removed from the image when converting an image into a captioned image.
345-
// #TINY-11670
333+
=== Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips
334+
// #TINY-11768
346335

347-
Previously, an issue occurred where toggling a caption on a floating image did not remove the float property from the image, causing the caption text to be incorrectly positioned.
336+
In previous versions of {productname}, hovering over toolbar menu item would display both a custom tooltip and the default browser tooltip. This caused confusing behavior, as the custom tooltip was difficult to read due to the browser tooltip overlapping it.
348337

349-
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.
338+
{productname} {release-version} resolves this issue by replacing the `title` attribute with the `aria-label` attribute for toolbar groupings, preventing the default browser tooltip from appearing.
350339

351-
=== Fixed keyboard navigation for size inputs in context forms.
352-
// #TINY-11394
340+
=== Toolbar text field was not properly rendering focus.
341+
// #TINY-11658
353342

354-
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.
343+
Previously, input elements lacked styling logic to display a border when focused, resulting in no visible indication of focus.
344+
This issue has been resolved in {productname} {release-version}. Input elements now correctly display a border when focused, ensuring improved visual feedback.
355345

356-
With the release of {productname} {release-version}, keyboard navigation has been implemented for these elements, ensuring seamless accessibility and improved usability.
346+
=== Dialog menu dropdowns now close when scrolling the editor container.
347+
// #TINY-11398
348+
349+
Previously, dialog menu dropdowns were not positioned correctly after scrolling the editor container, causing them to remain visible even when the editor was no longer in view. This resulted in dropdowns being displayed without their corresponding dialog context.
350+
351+
{productname} {release-version} updates the behavior to ensure that dialog menu dropdowns close on the window scroll event, preventing them from appearing out of context.
352+
353+
=== Expanding selection to a word didn't work inside inline editing host elements.
354+
// #TINY-11304
355+
356+
Previously, an issue occurred where the selection did not expand as expected when using the `editor.selection.expand({ type: 'word' })` API when the selection was within an inline edit host element inside a non-editable parent.
357+
358+
This has been resolved in {productname} {release-version}, ensuring that the expanded selection now remains within the boundaries of the editable host element.
357359

358360
[[known-issues]]
359361
== Known issues

0 commit comments

Comments
 (0)