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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/7.6.0-release-notes.adoc
+78-1Lines changed: 78 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,8 +168,41 @@ In {productname} {release-version}, the focus behaviour has now been improved in
168
168
* Creating a new comment within an existing conversation now brings the focus to the corresponding conversation card.
169
169
* Starting a new conversation now brings the focus to the newly created conversation card.
170
170
171
+
==== Added tooltips to conversation and comment kebab menus
172
+
173
+
In previous versions of **Comments**, the kebab menu button in the comments sidebar was missing a tooltip for users relying on assistive technologies.
174
+
175
+
{productname} {release-version} addresses this issue, by adding an `aria-label` with the description "Comment Actions" to the sidebar comment menu button, ensuring a tooltip is displayed on hover. This update improves accessibility and aligns the user experience across different menu buttons.
176
+
171
177
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
172
178
179
+
=== Comments
180
+
181
+
The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
182
+
183
+
**Comments** Premium plugin includes the following fixes and improvements.
184
+
185
+
==== The caret in comment textarea returned to its previous location before closing the mentions menu by selecting with the mouse.
186
+
// #TINY-11453
187
+
188
+
Previously, when closing the Mentions dropdown in a Comment textarea by clicking away, the caret would revert to its previous position, disregarding the user’s mouse-click location. This issue occurred because the logic for handling caret positioning did not account for mouse interactions, resulting in a disjointed and confusing user experience.
189
+
190
+
In {productname} {release-version} this issue was addressed. Now, the caret now accurately reflects the user’s intended position when the Mentions dropdown is closed via a mouse-click.
191
+
192
+
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
193
+
194
+
=== Enhanced Code Editor
195
+
// #TINY-11298
196
+
197
+
The {productname} {release-version} release includes an accompanying release of the **Enhanced Code Editor** premium plugin.
198
+
199
+
**Enhanced Code Editor** Premium plugin includes the following fix.
200
+
201
+
==== Spelling error in tooltip for `fullscreen` toggle button
202
+
203
+
The tooltip for the `fullscreen` toggle button was incorrectly labeled as `Fullsceen`. {productname} {release-version} addresses this issue which has now been corrected to `Fullscreen`.
204
+
205
+
For information on the **Enhanced Code Editor** plugin, see: xref:advcode.adoc[Enhanced Code Editor]
@@ -213,7 +246,33 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
213
246
=== <TINY-vwxyz 1 changelog entry>
214
247
// #TINY-vwxyz1
215
248
216
-
== New `+disabled+` option for disabling all user interactions
249
+
=== Add Labels and Groups for Context Toolbar Buttons
250
+
// #TINY-11095
251
+
252
+
The release of {productname} {release-version} introduces the ability to organize context toolbar buttons into groups with optional labels or titles. This enhancement, available from {productname} 7.6.0 onward, improves toolbar usability by enabling clearer categorization of buttons.
253
+
254
+
The `items` object structure now supports defining groups with an optional `name` property for titles or a `label` property for identifying the group. This feature allows developers to create more intuitive and accessible toolbars by visually segmenting functionality.
255
+
256
+
Example of a context toolbar configuration with groups and labels:
257
+
258
+
.Example
259
+
[source,js]
260
+
----
261
+
items: [
262
+
{
263
+
name: 'Formatting', // Optional, used as the group's title
For more details on configuring context toolbar groups and labels, see: xref:contexttoolbar.adoc#add-labels-and-groups-for-context-toolbar-buttons[Context Toolbar].
274
+
275
+
=== New `+disabled+` option for disabling all user interactions
217
276
218
277
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.
219
278
@@ -245,6 +304,24 @@ A new `+onSetup+` API has been introduced for context forms, enabling integrator
245
304
246
305
For more details, refer to xref:contextform.adoc#form[Context Form].
247
306
307
+
=== Added placeholder support for context form input fields
308
+
// #TINY-11459
309
+
310
+
A new `placeholder` option has been introduced to the context form API, addressing the need for inline guidance within input fields. This feature enables developers to specify placeholder text that appears inside input fields until the field is focused or a value is entered. By providing contextual hints, this enhancement improves usability and enhances the user experience.
311
+
312
+
.Example: Using a placeholder in a context form input field
== Add labels and groups for context toolbar buttons
32
+
33
+
From {productname} 7.6.0 onward, registering a context toolbar allows specifying `items` as an object that supports grouping with optional names and labels. This improvement enhances toolbar usability by organizing buttons into titled or labeled groups.
34
+
35
+
The object structure takes two optional properties: `name` and `label`.
36
+
37
+
* `name`: property is used as the group's title for the group that contains the buttons.
38
+
* `label`: property is used as a label for each group of buttons.
39
+
40
+
[NOTE]
41
+
If neither `name` nor `label` is specified, the behavior defaults to ungrouped buttons.
42
+
43
+
The object structure for `items` is as follows:
44
+
45
+
.Example of a context toolbar configuration with groups and labels
46
+
[source,js]
47
+
----
48
+
items: [
49
+
{
50
+
name: 'Formatting', // Optional, used as the group's title
There is an `+editor+` event called `+contexttoolbar-show+` that can be fired to show a context toolbar at the current selection. The event takes a parameter `+toolbarKey+` which specifies the name of the registered context form or context toolbar to show.
0 commit comments