Merge branch 'feature/7.7.0/DOC-3132' into feature/7.7.0/DOC-3132_TINY-11746

Author: kemister85

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

@@ -24,6 +24,19 @@ include::partial$misc/admon-releasenotes-for-stable.adoc[]
 
 The following premium plugin updates were released alongside {productname} {release-version}.
 
+=== Export to PDF
+
+The {productname} {release-version} release includes an accompanying release of the **Export to PDF** premium plugin.
+
+**Export to PDF** Premium plugin includes the following improvement.
+
+==== The `format` property in `exportpdf_converter_options` now accepts lowercase  
+// #TINY-11722  
+
+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.  
+
+For information on the **Export to PDF** plugin, see: xref:exportpdf.adoc[Export to PDF].
+
 === Export to Word
 
 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
 
 **Comments** includes the following fixes.
 
+==== Editing a comment and adding a mention to the comment would result in the mention not showing correctly after saving the comment.
+// #TINY-11602
+
+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.
+
+{productname} {release-version} resolves this issue by ensuring that newly added mentions to an existing comment are displayed correctly.
+
 ==== Pressing Keyboard shorctut `cmd+alt+m` when cursor is on annotated content now opens and focuses the reply textarea.
 // #TINY-11321
 
@@ -74,6 +94,27 @@ In previous versions of **Comments**, the side panel header blended into the bod
 
 {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.
 
+==== Editor now dispatches `Change` event after a comment is edited or a reply is created.
+// #TINY-11802
+
+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.
+
+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.
+
+==== Comment card jumps when editing a large comment in Chrome
+// #TINY-11729
+
+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.  
+
+{productname} {release-version} resolves this issue by ensuring the comment sidebar remains stable, preventing unintended jumps when editing large comments. 
+
+==== Closing the comment kebab menu with keyboard would result in the editor dispatching a `blur` event.
+// #TINY-11172
+
+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.
+
+{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.
+
 For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].
 
 === Image Optimizer
@@ -107,6 +148,19 @@ This caused confusion in identifying the problem during setup.
 
 {productname} {release-version} addresses this by providing a more detailed error message when the `uploadcare_public_key` is not configured.
 
+==== Toolbar text field was not properly rendering focus.
+// #TINY-11658
+
+Previously, input elements lacked styling logic to display a border when focused, resulting in no visible indication of focus.
+This issue has been resolved in {productname} {release-version}. Input elements now correctly display a border when focused, ensuring improved visual feedback.
+
+==== It was possible to `tab` to a toolbar group that had all children disabled.
+// #TINY-11665
+
+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.
+
+{productname} {release-version} resolves this issue by ensuring that containers with only disabled elements are no longer focusable, preventing unintended focus behavior.
+
 For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
 
 === Revision History
@@ -124,17 +178,35 @@ This improvement enhances access control within the **Revision History** plugin,
 
 For more information on the **Revision History** plugin, see: xref:revisionhistory.adoc[Revision History].
 
+=== Accessibility Checker
+
+The {productname} {release-version} release includes an accompanying release of the **Accessibility Checker** premium plugin.
+
+**Accessibility Checker** includes the following fix.
+
+==== Update form validation error message color to be the same as the error text color.
+// #TINY-11657
+
+In previous versions of the **Accessibility Checker** premium plugin, the form validation error message had insufficient color contrast in dark mode, failing to meet link:https://www.w3.org/WAI/WCAG2AA-Conformance[WCAG AA] standards and reducing visibility.
+
+With the release of {productname} {release-version}, this issue has been resolved by updating the error message color to be the same as the error text color, ensuring improved visibility and compliance with link:https://www.w3.org/WAI/WCAG2AA-Conformance[WCAG AA] contrast standards.
+
+For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.adoc[Accessibility Checker].
 
 [[improvements]]
 == Improvements
 
-{productname} {release-version} also includes the following improvement<s>:
+{productname} {release-version} also includes the following improvements:
 
-=== <TINY-vwxyz 1 changelog entry>
-// #TINY-vwxyz1
+=== Extended the `forceReadOnly` functionality to support the new `disabled` option in addition to readonly mode.
+// #TINY-11490
 
-// CCFR here.
+In previous versions of {productname}, the editor would transition to read-only mode if the API key was missing, invalid, or if the domain was invalid. With the release of {productname} {release-version}, this behavior has been updated to instead activate disabled mode in these scenarios.
+
+===  Added `link_attributes_postprocess` option that allows overriding attributes of a link inserted through the link dialog.
+// #TINY-11707
 
+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.
 
 [[additions]]
 == Additions
@@ -152,6 +224,11 @@ For more information on the **Revision History** plugin, see: xref:revisionhisto
 
 {productname} <x.y[.z]> also includes the following bug fix<es>:
 
+=== Dialog menu dropdowns now close when scrolling the editor container.
+// #TINY-11398
+
+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.
+
 === The `insertContent` API was not replacing selected non-editable elements correctly.
 // #TINY-11714
 
@@ -178,13 +255,34 @@ the help dialog would not open if the plugin was disabled, leading to confusion.
 
 {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.".
 
+=== The `semantics` element in MathML was not properly preserved when `annotation` elements were allowed.
+// #TINY-11755
+
+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.
+
+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.
+
 === Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips
 // #TINY-11768
 
 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.
 
 {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.
 
+=== The `float` property was not properly removed from the image when converting an image into a captioned image.
+// #TINY-11670
+
+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.
+
+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.
+
+=== Fixed keyboard navigation for size inputs in context forms.
+// #TINY-11394
+
+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.
+
+With the release of {productname} {release-version}, keyboard navigation has been implemented for these elements, ensuring seamless accessibility and improved usability.
+
 [[known-issues]]
 == Known issues
 

modules/ROOT/pages/changelog.adoc

@@ -4,6 +4,52 @@
 
 NOTE: This is the {productname} Community version changelog. For information about the latest {cloudname} or {enterpriseversion} Release, see: xref:release-notes.adoc[{productname} Release Notes].
 
+== xref:7.7.0-release-notes.adoc[7.7.0 - 2025-02-19]
+
+=== Added
+* `link_attributes_postprocess` option that allows overriding attributes of a link that would be inserted through the link dialog.
+// #TINY-11707
+
+=== Improved
+* Improved visual indication of a keyboard focus for a comment annotation when there is an image inside.
+// #TINY-11596
+* Not specifying a notification type (or specifying incorrect one) now defaults to 'info'.
+// #TINY-11661
+* Improved visual separation of comments side panel header.
+// #TINY-11715
+
+=== Changed
+- Changed the `link` plugin behavior to move the cursor behind a link when inserted or edited via the UI. Patch contributed by Philipp91.
+// ##GH-9998
+
+=== Fixed
+* Keyboard navigation for size inputs in context forms.
+// #TINY-11394
+* Keyboard navigation for context form sliders.
+// #TINY-11482
+* The `insertContent` API was not replacing selected non-editable elements correctly.
+// #TINY-11714
+* Context toolbar inputs had incorrect margins.
+// #TINY-11624
+* Iframe aria text used to suggest to open help dialog even when the help plugin was not enabled.
+// #TINY-11672
+* Preview Dialog incorrectly opened anchor links in a new tab.
+// #TINY-11740
+* The `float` property was not properly removed on the image when converting a image into a captioned image.
+// #TINY-11670
+* Expanding selection to a word didn't work inside inline editing host elements.
+// #TINY-11304
+* The `semantics` element in MathML was not properly retained when `annotation` elements was allowed.
+// #TINY-11755
+* It was possible to tab to a toolbar group that had all children disabled.
+// #TINY-11665
+* Keyboard navigation would get stuck on the 'more' toolbar button.
+// #TINY-11762
+* Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips.
+// #TINY-11768
+* Toolbar text field was properly rendering focus.
+// #TINY-11658
+
 == xref:7.6.1-release-notes.adoc[7.6.1 - 2025-01-22]
 
 === Fixed

modules/ROOT/pages/cloud-troubleshooting.adoc

@@ -175,4 +175,6 @@ This message is shown when {productname} is loaded from a domain that has not be
 
 ==== Solution
 
-Please request that your admin add this domain to the approved domains in the Customer Portal. For more information see xref:cloud-troubleshooting.adoc#domain-not-registered[Domain not registered]
+Please request that your admin add this domain to the approved domains in the Customer Portal. For more information see xref:cloud-troubleshooting.adoc#domain-not-registered[Domain not registered]
+
+NOTE: From xref:7.6.0-release-notes.adoc[{productname} 7.6.0] onwards, the editor uses disabled mode instead of read-only mode.

modules/ROOT/pages/link.adoc

@@ -46,6 +46,8 @@ include::partial$configuration/link_rel_list.adoc[leveloffset=+1]
 
 include::partial$configuration/link_target_list.adoc[leveloffset=+1]
 
+include::partial$configuration/link_attributes_postprocess.adoc[leveloffset=+1]
+
 include::partial$misc/plugin-toolbar-button-id-boilerplate.adoc[]
 
 include::partial$misc/plugin-menu-item-id-boilerplate.adoc[]

modules/ROOT/partials/configuration/link_attributes_postprocess.adoc

@@ -0,0 +1,26 @@
+[[link_attributes_postprocess]]
+== `+link_attributes_postprocess+`
+
+This option allows overriding attributes of an inserted link.
+
+*Type:* `+Function+`
+
+*Default value:* `+undefined+`
+
+=== Example: using `+link_attributes_postprocess+`
+
+[source,js]
+----
+tinymce.init({
+  selector: 'textarea', // change this value according to your HTML
+  plugins: 'link',
+  toolbar: 'link',
+  link_attributes_postprocess: (attrs) => {
+    console.log(attrs);
+    if (attrs.rel) {
+      attrs.rel += 'noreferrer';
+    }
+  }
+});
+
+----