{productname} 7.7.0 was released for {enterpriseversion} and {cloudname} on <weekday>, <month> <DD><st|nd|rd|th>, <YYYY>. These release notes provide an overview of the changes for {productname} 7.7.0, including:
The following premium plugin updates were released alongside {productname} 7.7.0.
The {productname} 7.7.0 release includes an accompanying release of the Export to PDF premium plugin.
Export to PDF Premium plugin includes the following improvement.
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.
The {productname} 7.7.0 release includes an accompanying release of the Export to Word premium plugin.
Export to Word includes the following fix.
Previously, the Export to Word premium plugin did not support watermarks, preventing integrators from adding them to exported Word documents.
With the release of {productname} 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.
The {productname} 7.7.0 release includes an accompanying release of the Advanced Typography premium plugin.
Advanced Typography includes the following fix.
Previously, an issue was identified where Ukrainian and Serbian were incorrectly spelt in the typography plugin.
{productname} 7.7.0 addresses this by fixing the spelling.
For information on the Advanced Typography plugin, see: Advanced Typography.
The {productname} 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.
{productname} 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.
{productname} 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.
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.
{productname} 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.
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 {productname} 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.
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} 7.7.0 resolves this issue by ensuring the comment sidebar remains stable, preventing unintended jumps when editing large comments.
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} 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.
The {productname} 7.7.0 release includes an accompanying release of the Image Optimizer premium plugin.
Image Optimizer includes the following fixes and improvements.
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."
{productname} 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.
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.
{productname} 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.
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.
{productname} 7.7.0 addresses this by providing a more detailed error message when the uploadcare_public_key is not configured.
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} 7.7.0. Input elements now correctly display a border when focused, ensuring improved visual feedback.
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} 7.7.0 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: Image Optimizer.
{productname} <x.y[.z]> also includes the following bug fix<es>:
Previously in {productname}, 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.
{productname} 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.
In earlier versions of {productname}, 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.
{productname} 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.
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.
{productname} 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.".
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} 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.
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} 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.
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 {productname} 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.