TinyMCE 7.7.0

These are the Tiny Cloud and TinyMCE Enterprise release notes. For information on the latest community version of TinyMCE, see the TinyMCE Changelog.

Overview

TinyMCE 7.7.0 was released for TinyMCE Enterprise and Tiny Cloud on Thursday, February 20th, 2025. These release notes provide an overview of the changes for TinyMCE 7.7.0, including:

Accompanying Premium self-hosted server-side component changes

The TinyMCE 7.7.0 release includes accompanying changes affecting the TinyMCE self-hosted services for the following plugin:

  • Spell Checker plugin tinymcespellchecker.

For information on:

The Java server-side component has been updated to the following version:

  • ephox-spelling.war: 2.128.3

Updating the self-hosted server-side components

The new versions of the server-side services provide updates for the Java-based server-side components. To deploy the updated version of the server-side components:

  1. Update your Java Application Server to the minimum required version:

    • Eclipse Jetty:

      • 9.4+

    • WebSphere Application Server (WAS) 8 or later

    • Apache Tomcat:

      • 10 (See note below)

      • 9+

      • 8.5.12+

      • 8.0.42+

      • 7.0.76+

      Tomcat 10 will require WAR files to be placed in the webapp-javaee directory rather than the webapps directory due to the change to Jakarta servlets. Jetty 11 is not currently supported due to this change.

  2. Replace the existing server-side .war files with the .war files bundled with TinyMCE 7.7.0 or later.

For information on:

There are no functionality changes in these updated server-side components.

Accompanying Premium plugin changes

The following premium plugin updates were released alongside TinyMCE 7.7.0.

Comments

The TinyMCE 7.7.0 release includes an accompanying release of the Comments premium plugin.

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.

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.

TinyMCE 7.7.0 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.

Previously, an issue was identified where pressing the keyboard shortcut cmd-alt-m on Mac and ctrl-alt-m on Windows while the cursor was on annotated content and the comments sidebar was open resulted in the focus shifting to the corresponding comment, which was not the desired behavior.

TinyMCE 7.7.0 fixes this by ensuring that the focus now moves to the reply text area instead of the corresponding comment. This matches the behavior when the "Add New Comment" button is clicked, resulting in more consistent functionality.

Improved visual separation of comments side panel header.

In previous versions of Comments, the side panel header blended into the body, resulting in a lack of visual separation. This made the UI appear less polished and dimensional.

TinyMCE 7.7.0 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.

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 Save plugin, the save button remained disabled after replying to or editing a comment, which was not the expected behavior.

In TinyMCE 7.7.0, 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

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.

TinyMCE 7.7.0 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.

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.

TinyMCE 7.7.0 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: Comments.

Image Optimizer

The TinyMCE 7.7.0 release includes an accompanying release of the Image Optimizer premium plugin.

Image Optimizer includes the following fixes and improvements.

Some image file extensions would sometimes be incorrectly considered unsupported.

Previously, an issue was identified where .jfi and .jif file extensions were incorrectly considered unsupported due to the validation logic.

As a result, these extensions were blocked, and users encountered the error message: "Failed to upload: The image is not a supported file format."

TinyMCE 7.7.0 resolves this issue by fixing the validation logic to correctly detect the MIME type of uploaded images, ensuring that users can now successfully upload .jfi and .jif files.

Dropping files on the placeholder would sometimes insert the image in an incorrect location.

Previously, an issue was identified where the drag-and-drop functionality on an image placeholder in a table would insert the image outside of the table cell. This resulted in unpredictable behavior when users dragged and dropped an image into the image placeholder.

TinyMCE 7.7.0 resolves this issue by making it so that that the image placeholder handles the drop event instead of the editor content element. This improvement provides predictable and consistent drag-and-drop behavior for image placeholders in Image Optimizer.

Some error messages are now more descriptive.

Previously, error messages were unclear when the uploadcare_public_key was not configured with a valid API key. This caused confusion in identifying the problem during setup.

TinyMCE 7.7.0 addresses this by providing a more detailed error message when the uploadcare_public_key is not configured.

Part of the placeholder border was not visible during loading.

Previously, the image upload placeholder had a border rendering issue, which affected the visual consistency of the UI during the upload process.

TinyMCE 7.7.0 addresses this by refining the CSS to ensure the border is properly rendered, resulting in a more polished and design-compliant user interface.

For information on the Image Optimizer plugin, see: Image Optimizer.

Export to PDF

The TinyMCE 7.7.0 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

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: Export to PDF.

Export to Word

The TinyMCE 7.7.0 release includes an accompanying release of the Export to Word premium plugin.

Export to Word includes the following fix.

A document watermark can now be specified for the exported file

Previously, the Export to Word premium plugin did not support watermarks, preventing integrators from adding them to exported Word documents.

With the release of TinyMCE 7.7.0 watermark functionality has been introduced, enabling watermarks to be included in exported documents.

For information on the Export to Word plugin, see: Export to Word.

Advanced Typography

The TinyMCE 7.7.0 release includes an accompanying release of the Advanced Typography premium plugin.

Advanced Typography includes the following fix.

Serbian and Ukrainian languages were spelled incorrectly.

Previously, an issue was identified where Ukrainian and Serbian were incorrectly spelt in the typography plugin.

TinyMCE 7.7.0 addresses this by fixing the spelling.

For information on the Advanced Typography plugin, see: Advanced Typography.

Enhanced Code Editor

The TinyMCE 7.7.0 release includes an accompanying release of the Enhanced Code Editor premium plugin.

Enhanced Code Editor includes the following fix.

The cursor was sometimes incorrectly placed after opening the source code editor.

In previous versions of the Enhanced Code Editor premium plugin, the cursor was sometimes incorrectly positioned when opening the source code editor. This issue occurred when automatic formatting was enabled, particularly if the cursor was placed after indentations, leading to unpredictable cursor behavior.

TinyMCE 7.7.0 addresses this by applying optional formatting before determining the cursor’s position, ensuring consistent and reliable cursor placement in the source code editor.

For information on the Enhanced Code Editor plugin, see: Enhanced Code Editor.

Revision History

The TinyMCE 7.7.0 release includes an accompanying release of the Revision History premium plugin.

Revision History includes the following addition.

New revisionhistory_allow_restore option to control restoration of old revisions

TinyMCE 7.7.0 introduces a new revisionhistory_allow_restore option, which provides a way to control if a user can restore revisions. By default, it is set to true, setting it to false prevents users from restoring previous versions.

This improvement enhances access control within the Revision History plugin, providing greater flexibility for managing revision restoration.

For more information on the Revision History plugin, see: Revision History.

Accessibility Checker

The TinyMCE 7.7.0 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.

In previous versions of the Accessibility Checker premium plugin, the form validation error message had insufficient color contrast in dark mode, failing to meet WCAG AA standards and reducing visibility.

With the release of TinyMCE 7.7.0, 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 WCAG AA contrast standards.

For information on the Accessibility Checker plugin, see: Accessibility Checker.

Improvements

TinyMCE 7.7.0 also includes the following improvements:

Improved visual indication of keyboard focus for a comment annotation when there is an image inside.

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.

With the release of TinyMCE 7.7.0, 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.

Not specifying a notification type (or specifying an incorrect one) now defaults to 'info'.

In earlier versions of TinyMCE, an undefined or incorrect type property in the notification manager resulted in irregular notifications with no background and a placeholder icon, making them difficult to read.

With the release of TinyMCE 7.7.0, this behavior has been improved. The type property now defaults to info when an invalid or missing value is detected, resulting in a proper looking notification that is easy to understand.

Extended the forceReadOnly functionality to support the new disabled option in addition to readonly mode.

In previous versions of TinyMCE, 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 TinyMCE 7.7.0, this behavior has been updated to instead activate disabled mode in these scenarios.

Additions

TinyMCE 7.7.0 also includes the following addition:

Previously in the Link plugin, there was no ability to override attributes of a link. With the release of TinyMCE 7.7.0, a new option link_attributes_postprocess has been added that allows this functionality.

Bug fixes

TinyMCE 7.7.0 also includes the following bug fixes:

Fixed keyboard navigation for size inputs in context forms.

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 TinyMCE 7.7.0, keyboard navigation has been implemented for these elements, ensuring seamless accessibility and improved usability.

The insertContent API was not replacing selected non-editable elements correctly.

Previously in TinyMCE, an issue was identified where, if an inline non-editable element was the only child of a block, inserting content would not replace the element. As a result, integrators were unable to insert content into inline non-editable elements.

TinyMCE 7.7.0 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.

Context toolbar inputs had incorrect margins.

Previously, input elements within the contextual toolbar were not styled correctly and overflowed when using the fluent, snow, and jam premium skins. This issue arose because these skins modified toolbar element properties such as padding, height, and width, but the adjustments were not applied consistently to input elements. As a result, the UI appeared misaligned and less polished.

In TinyMCE 7.7.0, this issue has been resolved. Contextual toolbar elements, including buttons and inputs, now use the same padding and height values, ensuring a consistent and polished appearance.

Iframe aria text used to suggest to open help dialog even when the help plugin was not enabled.

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, the help dialog would not open if the plugin was disabled, leading to confusion.

TinyMCE 7.7.0 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.".

In earlier versions of TinyMCE, an issue was identified in dialogs like the Preview dialog, where anchor links behaved inconsistently when clicked within the editor.

The problem was that clicking an anchor link in a dialog caused the editor to attempt to open the link in a new browser tab. This behavior differed from the expected functionality in the editor, where clicking an anchor link navigates to the corresponding anchor element. This resulted in a poor user experience as users could not engage with anchor links as expected.

TinyMCE 7.7.0 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.

The float property was not properly removed from the image when converting an image into a captioned image.

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 TinyMCE 7.7.0, 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.

Expanding selection to a word didn’t work inside inline editing host elements.

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.

This has been resolved in TinyMCE 7.7.0, ensuring that the expanded selection now remains within the boundaries of the editable host element.

The semantics element in MathML was not properly preserved when annotation elements were allowed.

Previously, in TinyMCE, 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 TinyMCE 7.7.0, 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.

It was possible to tab to a toolbar group that had all children disabled.

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.

TinyMCE 7.7.0 resolves this issue by ensuring that containers with only disabled elements are no longer focusable, preventing unintended focus behavior.

Keyboard navigation would get stuck on the 'more' toolbar button.

Previously, an issue was identified where keyboard navigation using the Tab key would become stuck at the "Show More" button in the toolbar. This occurred because hidden toolbar elements were incorrectly detected as valid tab targets, disrupting seamless navigation and negatively impacting the user experience.

In TinyMCE 7.7.0, 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.

Toolbar groups had both a title attribute and a custom tooltip, causing overlapping tooltips

In previous versions of TinyMCE, 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.

TinyMCE 7.7.0 resolves this issue by replacing the title attribute with the aria-label attribute for toolbar groupings, preventing the default browser tooltip from appearing.

Toolbar text field was not properly rendering focus.

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 TinyMCE 7.7.0. Input elements now correctly display a border when focused, ensuring improved visual feedback.

Known issues

This section describes issues that users of TinyMCE 7.7.0 may encounter and possible workarounds for these issues.

There one known issue in TinyMCE 7.7.0.

Missing Hebrew translation for Blockquote toolbar button tooltip

The Blockquote toolbar button tooltip does not display a translation for Hebrew. This issue affects users who rely on localized tooltips for accessibility and usability.

Status: Currently under investigation.