TinyMCE 8.9.0

Previously, the Comments plugin highlighted commented content only while the Comments sidebar was open. Closing the sidebar removed the highlighting from the editor content, so commented content was easy to overlook and users could overwrite it without warning.

In TinyMCE 8.9.0, the Comments plugin offers the tinycomments_always_show_highlights option. When this option is set to true, commented content remains highlighted whether the Comments sidebar is open or closed. This option defaults to false, which preserves the existing behavior.

Previously, the Comments plugin removed the highlighting while the Comments sidebar was closed, so users could not reopen a conversation from the editor content.

In TinyMCE 8.9.0, when the tinycomments_always_show_highlights option is set to true, selecting highlighted content reopens the closed Comments sidebar.

Previously, the content styles of the Comments plugin fixed the Comments sidebar at 300 pixels wide, and a user could not change that width.

In TinyMCE 8.9.0, the Comments sidebar is registered with the resizable property set to true, so a user can resize it by dragging its edge. The sidebar opens at the width set by the sidebar_width option, which defaults to 440 pixels, so the Comments sidebar is wider by default than in earlier versions. Setting sidebar_width to 300 restores the previous width, and applies that width to every resizable sidebar in the editor.

For information on the Comments plugin, see: Comments.

Previously, when the document content exceeded the context limit of the AI service, a quick action or review failed and reported the general message An error occurred while processing the AI response. That message did not identify the length of the document as the cause.

In TinyMCE 8.9.0, the TinyMCE AI plugin shows This document is too long for the AI to process at once. when a quick action or review fails for this reason. The message states the limit without suggesting a corrective action, because the full document is always sent to the AI service.

Previously, adding a malformed URL as a context source in the Chat sidebar reported Provided URL is not valid. That message did not indicate what part of the address to correct.

In TinyMCE 8.9.0, the TinyMCE AI plugin shows This URL isn't valid. Check the full, correct web address and try again. in the same situation. The message applies to the format of the address. A well-formed address that points to a page that cannot be reached is still accepted and sent for processing.

Previously, selecting a welcome action in the AI Chat sidebar moved focus into the editor before running the action’s command. Focusing the editor scrolls the content to the current selection, and when no selection had been made, that position was the start of the content. Users who had scrolled through a document lost that scroll position as soon as a welcome action was selected.

In TinyMCE 8.9.0, the TinyMCE AI plugin runs welcome action commands without moving focus into the editor. Selecting a welcome action leaves the editor scroll position and focus unchanged. Welcome actions are configured with the tinymceai_chat_welcome_actions option.

Previously, the tooltips shown in the TinyMCE AI sidebars did not respond to Esc. These sidebars use their own tooltips, which were not connected to the editor keyboard shortcut that closes tooltips, so an open tooltip remained on screen until the pointer or focus moved elsewhere. Keyboard users could not dismiss a tooltip that obscured the interface.

In TinyMCE 8.9.0, pressing Esc closes an open tooltip in the TinyMCE AI sidebars.

Previously, text that sat directly alongside a nested list or table within the same container was not tracked as a block-level change, so the comparison that produces suggestions skipped it. Review mode showed that text as unchanged even when the review returned suggestions for it. Reviewers could not see or act on those suggestions, and the suggested edits were lost once the review was completed.

In TinyMCE 8.9.0, the TinyMCE AI plugin treats text alongside a nested list or table as a block-level change when preparing the document for comparison. Suggestions for that text now appear in the Review sidebar and in the document with the rest of the suggestions, and each one can be accepted or rejected as usual.

In TinyMCE 8.9.0, the TinyMCE AI plugin registers an editor command for each built-in review, such as TinyMCEAIReviewProofread and TinyMCEAIReviewToneProfessional. The plugin also registers the TinyMCEAIReviewCustom command, which runs a review from a custom prompt or runs an integrator-defined review by identifier. Each command opens the Review sidebar and runs the review, with the same result as selecting that review in the sidebar. Previously, a review could only be started from the Review sidebar, so integrations could not start one from their own interface.

For the command identifiers and the values accepted by TinyMCEAIReviewCustom, see TinyMCE AI plugin commands.

Previously, when the AI service rejected a file added as a context source in the Chat sidebar, the sidebar reported the failure using the message returned by the service, such as Content too large. Those messages described the service response rather than the file, so users could not tell which property of the file caused the failure, or what to try instead.

In TinyMCE 8.9.0, the TinyMCE AI plugin shows a message for each file failure it can identify:

When the cause cannot be identified, the plugin shows This file can't be added. Try a smaller file, or a different file type.

Previously, when a chat message combined with the conversation history together exceeded the context limit of the AI service, the Chat sidebar reported the failure with the general message An error occurred while processing the AI response. That message did not identify the size of the request as the cause, so users could not tell whether to shorten the message, start a new conversation, or try again unchanged.

In TinyMCE 8.9.0, the TinyMCE AI plugin shows This message is too long for the AI to process. Try a shorter message, or start a new chat. when the AI service reports that a chat request exceeds the context limit. The message names the cause and describes the two ways to continue.

Previously, when the text typed into the Chat sidebar exceeded the maximum length that the AI service accepts for a single message, the request failed and the Chat sidebar reported it with the general message An error occurred while processing the AI response. That message did not identify the length of the typed text as the cause, so users could not tell that shortening the message would resolve the failure.

In TinyMCE 8.9.0, the TinyMCE AI plugin shows This prompt is too long. Try a shorter one. when the typed text exceeds that limit. This message applies to the typed message on its own, and is distinct from the message shown when a message and the conversation history together exceed the context limit of the AI service.

Previously, the TinyMCE AI plugin applied only the current document to the context of a new AI Chat conversation. Users had to manually add every other context source, such as a style guide or reference document, to each new conversation.

In TinyMCE 8.9.0, the function supplied to tinymceai_chat_fetch_sources can resolve to an object with a menu property, holding the source groups shown in the sources menu, and a defaults property, holding an array of source identifiers. The plugin adds each source listed in defaults to the context of every new conversation, and shows it as selected in the sources menu. Users can remove a default source from a conversation and add it again from the sources menu.

Identifiers listed in defaults without a matching source in sources are not added to the context, and the plugin logs an error in the browser console.

The option continues to accept a function that resolves to an array of source groups, so existing configurations are unaffected.

For details on configuring conversation context, see Adding custom context sources.

Previously, the scroll position was not carried between the editor content and the AI preview. Opening the preview, running a review, or applying a quick action could move the viewport away from the part of the document being worked on, so users lost their place.

In TinyMCE 8.9.0, the TinyMCE AI plugin records the content block nearest to the current scroll position and restores the view to that block. The position is preserved when opening the preview, running a review, and applying a quick action, and it is restored to the same block even when the content is a different height in the editor and in the preview.

In TinyMCE 8.7.0, the icon-only buttons in the AI suggestion preview were replaced with labeled Apply and Skip buttons.

In TinyMCE 8.9.0, the TinyMCE AI plugin restores the icon-only buttons used before TinyMCE 8.7.0. A checkmark button applies the suggestion and a close button skips it, and each button shows a tooltip that names its action, Apply suggestion and Skip suggestion. The apply button remains the primary action, and the spacing of the preview toolbar is unchanged from TinyMCE 8.7.0.

For information on the TinyMCE AI plugin, see: TinyMCE AI.