Merge branch 'feature/7.6.0/DOC-2578' into feature/7.6.0/DOC-2578_TINY-11592

Author: kemister85

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

@@ -64,6 +64,7 @@ The {productname} {release-version} release includes an accompanying release of
 **Accessibility Checker** Premium plugin includes the following fixes and improvements.
 
 ==== Improve editor content highlighting when using accessibility checker
+// #TINY-11463
 
 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.
 
@@ -75,9 +76,23 @@ For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.a
 
 The {productname} {release-version} release includes an accompanying release of the **Comments** premium plugin.
 
-**Comments** Premium plugin includes the following improvements.
+**Comments** includes the following fixes and improvements.
 
-=== Pressing Shift+Enter in Mentions in Comments dropdown should accept the active menu item
+==== Allow mentions in comments dropdown to flow freely outside of the editor container
+// #TINY-11504
+
+An issue was identified where the mentions in comments dropdown didn't freely expand to the available space alongside mentions in the editor. This was due to the dropdown being restricted within the sidebar area.
+
+In {productname} {release-version}, this issue has been resolved by allowing the mentions in comments dropdown to expand outside the sidebar area, making full use of the available space outside the editor and improving the overall user experience.
+
+==== Scroll to show action buttons when replying/editing a comment.
+// #TINY-11402
+
+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.
+
+{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.
+
+==== Pressing Shift+Enter in Mentions in Comments dropdown should accept the active menu item
 // #TINY-11455
 
 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.
@@ -91,6 +106,17 @@ Previously, the **Comments** plugin used a `14px` font size for the comment body
 
 This issue has been resolved in {productname} {release-version} by setting the comment body font size to `16px`, ensuring font size consistency between the **Comments** plugin and the editor UI.
 
+==== Editor Focus after Deleting a Comment
+// #TINY-11293
+
+Previously, the focus behaviour in the comments sidebar was observed to be inconsistent. When a user deleted a comment, the focus exited the comments sidebar and returned to the editor instead of returning to the conversation card. This also occurred when a new comment was created inside an existing conversation, and when an entire new conversation was created.
+
+In {productname} {release-version}, the focus behaviour has now been improved in the following situations:
+
+* Deleting a comment now returns the focus to the conversation card that contained the deleted comment.
+* Creating a new comment within an existing conversation now brings the focus to the corresponding conversation card.
+* Starting a new conversation now brings the focus to the newly created conversation card.
+
 For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
 
 
@@ -136,7 +162,20 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
 === <TINY-vwxyz 1 changelog entry>
 // #TINY-vwxyz1
 
+== New `+disabled+` option for disabling all user interactions
+
+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.
+
+.Example disabling all user interactions with the editor
+[source,js]
+----
+tinymce.init({
+  selector: 'textarea',  // Specify the target HTML element
+  disabled: true         // Disables all interactions with the editor
+});
+----
 
+For more information on the `+disabled+` option, see xref:editor-important-options.adoc#disabled[Disabled] option.
 
 [[additions]]
 == Additions
@@ -176,6 +215,18 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
 
 {productname} {release-version} also includes the following bug fixes:
 
+=== Removed title attribute from dialog tree elements as they already have a tooltip.
+// #TINY-11470
+
+Previously, an issue was identified with tooltips for tree structures where multiple tooltip systems displayed the same text simultaneously:
+
+. The browser's native tooltip, triggered by the `title` attribute, displayed the text.
+. {productname}'s custom tooltip functionality also displayed the text.
+
+As a consequence, this caused two tooltips with identical content to appear at the same time, leading to a confusing user experience, where the desired behavior was to show only the custom tooltip provided by {productname}.
+
+In {productname} {release-version}, this issue has been resolved. The `title` attribute is now automatically removed when the custom tooltip is applied, ensuring that only the custom tooltip is displayed. 
+
 === Tooltip would not show for group toolbar button.
 // #TINY-11391
 
@@ -190,7 +241,6 @@ Previously, there was an issue where changes to the row type in numbered tables
 
 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.
 
-
 [[security-fixes]]
 == Security fixes
 

modules/ROOT/pages/editor-important-options.adoc

@@ -35,6 +35,10 @@ include::partial$configuration/external_plugins.adoc[leveloffset=+1]
 
 include::partial$configuration/readonly.adoc[leveloffset=+1]
 
+== Setting the editor in a disabled state
+
+include::partial$configuration/disabled.adoc[leveloffset=+1]
+
 == Executing custom functions while the editor starts (initializes)
 
 include::partial$configuration/setup.adoc[leveloffset=+1]

modules/ROOT/pages/events.adoc

@@ -160,6 +160,7 @@ The following events are provided by the {productname} editor.
 |ObjectResized |`+{ target: HTMLElement, width: number, height: number, origin: string }+` |Fired when an object (such as an image) has finished being resized.
 |ObjectResizeStart |`+{ target: HTMLElement, width: number, height: number, origin: string }+` |Fired when an object (such as an image) is about to be resized.
 |SwitchMode |`+{ mode: string }+` |Fired when the editor mode is changed. The available modes are "design" and "readonly". Additional modes can be registered using {productname} API xref:apis/tinymce.editormode.adoc#register['tinymce.activeEditor.mode.register()'].
+|DisabledStateChange |+{ state: boolean }+ |Fired when the editor disabled mode state changes.
 |ScrollWindow |(Same data as the native https://developer.mozilla.org/en-US/docs/Web/API/Element/scroll_event[scroll event]) |Fired when the window has scrolled.
 |ResizeWindow |(Same data as the native https://developer.mozilla.org/en-US/docs/Web/API/Window/resize_event[resize event]) |Fired when the window is resized.
 |BeforeExecCommand |`+{ command: string, ui?: boolean, value?: any }+` |Fired before a command is executed.

modules/ROOT/partials/configuration/disabled.adoc

@@ -0,0 +1,23 @@
+[[disabled]]
+
+== `+disabled+`
+
+Disables all user interactions with the editor (including cursor placement, content modifications, UI components). This option provides behavior similar to the changes made to {productname} in 7.4.0 readonly mode. When enabled, the editor becomes completely non-interactive.
+
+To programmatically enable/disable the editor, use `+tinymce.activeEditor.options.set('disabled', false/true)+`.
+
+*Type:* `+Boolean+`
+
+*Default value:* `+false+`
+
+*Possible values:* `+true+`, `+false+`
+
+=== Example: using `+disabled+`
+
+[source,js]
+----
+tinymce.init({
+  selector: 'textarea',  // change this value according to your HTML
+  disabled: true
+});
+----