Skip to content

Commit edd9f4b

Browse files
authored
Merge branch 'feature/7.6.0/DOC-2578' into feature/7.6.0/DOC-2578_DOC-2586
2 parents 6d8a205 + ed53b54 commit edd9f4b

File tree

1 file changed

+44
-13
lines changed

1 file changed

+44
-13
lines changed

modules/ROOT/pages/7.6.0-release-notes.adoc

Lines changed: 44 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -57,17 +57,42 @@ 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+
=== Accessibility Checker
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 **Accessibility Checker** premium plugin.
6363

64-
**<Premium plugin name 1>** <Premium plugin name 1 version> includes the following <fixes, changes, improvements>.
64+
**Accessibility Checker** Premium plugin includes the following fixes and improvements.
6565

66-
==== <Premium plugin name 1 change 1>
66+
==== Improve editor content highlighting when using accessibility checker
67+
// #TINY-11463
6768

68-
// CCFR here.
69+
Previously, an issue involving the accessibility checker was identified where the content area highlights did not properly meet accessibility standards. This issue caused users with vision impairments to encounter difficulty in identifying the currently focused element.
70+
71+
In {productname} {release-version}, this issue has been resolved by unifying the color palette to meet accessibility color contrast standards, ensuring that all users can easily locate the currently focused element.
72+
73+
For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.adoc[Accessibility Checker].
74+
75+
=== Comments
76+
77+
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
78+
79+
**Comments** Premium plugin includes the following fixes and improvements.
80+
81+
==== Scroll to show action buttons when replying/editing a comment.
82+
// #TINY-11402
83+
84+
Previously, if a selected conversation card was positioned near the bottom of the sidebar, the reply/edit input field would be below the bottom of the sidebar resulting in the comment input field not being visible to the user.
85+
86+
{productname} {release-version} addresses this issue. Now, the sidebar scrolls to display the comment input field if the selected conversation card is positioned near the bottom of the sidebar. This ensures that the comment input field is always visible to the user.
87+
88+
==== Pressing Shift+Enter in Mentions in Comments dropdown should accept the active menu item
89+
// #TINY-11455
90+
91+
In previous versions of {productname}, the `Shift+Enter` key was not properly handled when used with mentions in comments. This led to a new line being inserted while the mentions dropdown remained open, resulting in inconsistent behavior compared to mentions within the editor.
6992

70-
For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
93+
In {productname} {release-version}, mentions in comments now handle the `Shift+Enter` key by inserting the highlighted user into the comment text area and closing the dropdown, ensuring consistent functionality across the editor and comment areas.
94+
95+
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
7196

7297

7398
[[accompanying-premium-plugin-end-of-life-announcement]]
@@ -112,8 +137,6 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
112137
=== <TINY-vwxyz 1 changelog entry>
113138
// #TINY-vwxyz1
114139

115-
// CCFR here.
116-
117140
== New `+disabled+` option for disabling all user interactions
118141

119142
A new `+disabled+` option has been introduced to {productname} in version {release-version}. This option allows integrators to disable all user interactions with the editor, including cursor placement, content modifications, and UI components. When set to `+true+`, the editor behaves similarly to the readonly mode changes introduced in {productname} 7.4.0 but ensures complete non-interactivity.
@@ -129,7 +152,6 @@ tinymce.init({
129152

130153
For more information on the `+disabled+` option, see xref:editor-important-options.adoc#disabled[Disabled] option.
131154

132-
133155
[[additions]]
134156
== Additions
135157

@@ -166,12 +188,21 @@ For more information on the `+disabled+` option, see xref:editor-important-optio
166188
[[bug-fixes]]
167189
== Bug fixes
168190

169-
{productname} {release-version} also includes the following bug fix<es>:
191+
{productname} {release-version} also includes the following bug fixes:
170192

171-
=== <TINY-vwxyz 1 changelog entry>
172-
// #TINY-vwxyz1
193+
=== Tooltip would not show for group toolbar button.
194+
// #TINY-11391
173195

174-
// CCFR here.
196+
Previously, an issue was identified where tooltips were not displayed when hovering over toolbar group buttons. This was due to replacing the `title` attribute with an `aria-label` attribute in xref:7.0-release-notes.adoc#improved-accessibility-for-interactive-elements-with-custom-tooltips[{productname} 7.0.0] without implementing the custom tooltip behavior for the toolbar group buttons.
197+
198+
In {productname} {release-version}, this issue has been resolved by applying the custom tooltip behavior to the toolbar group buttons, ensuring that tooltips are now displayed on hover.
199+
200+
=== Numbered table context menu not properly applying changes
201+
// #TINY-11383
202+
203+
Previously, there was an issue where changes to the row type in numbered tables were not properly applied. This occurred because the action of modifying the row type from a `+contentEditable="false"+` cell was being deliberately blocked.
204+
205+
In {productname} {release-version}, this issue has been resolved by removing the restriction on changing the row type from a `+contentEditable="false"+` cell. As a result, changes to the row type are now correctly applied.
175206

176207

177208
[[security-fixes]]

0 commit comments

Comments
 (0)