TinyMCE 8.7.0

Revisions now support an optional metadata property. Setting its source field to 'ai' marks a revision as AI-assisted, allowing integrators to track content produced by the TinyMCE AI plugin. An AI badge is rendered on the cards of AI-assisted revisions by default. Set the new revisionhistory_ai_attribution option to false to hide the badge.

For details on attributing revisions to AI, see Attributing AI-assisted revisions.

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

Suggested Edits now records edits made with the TinyMCE AI plugin as AI-assisted. An AI badge appears on the cards of those edits by default. Set the new suggestededits_ai_attribution option to false to hide the badge.

The suggestededits_model schema is now version 2. Models saved with version 1 are migrated automatically when loaded.

Suggested Edits now supports toggling suggestion tracking while editing. The new suggestededits-tracking toolbar button and menu item, along with the SuggestedEditsToggleTracking command, let users switch between tracking edits as suggestions or applying them directly to the content. The suggestededits_auto_approve configuration option now also controls their default state.

Because toggling tracking fundamentally changes the Suggested Edits experience, the button and menu item are not included by default. They must be explicitly added to the toolbar or menu in the editor configuration.

Previously, the SuggestedEditsHasChangesUpdate event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the hasChanges API could become outdated. As a result, any integration that relied upon the API would not receive an update when a review finished.

In TinyMCE 8.7.0, the SuggestedEditsHasChangesUpdate event fires whenever the value within the hasChanges API changes, including when a review completes.

For information on the Suggested Edits plugin, see: Suggested Edits.

The Export to PDF plugin now calls tinymce.editor.getContent() with an export property set to pdf. TinyMCE passes this property to the GetContent event and to serializer node filters, so an integrator can apply content filtering that targets a PDF export without affecting regular content retrieval.

For information on filtering content during an export, see: Export-specific content filtering. For information on the Export to PDF plugin, see: Export to PDF.

The Export to Word plugin now calls tinymce.editor.getContent() with an export property set to word. TinyMCE passes this property to the GetContent event and to serializer node filters, so an integrator can apply content filtering that targets a Word export without affecting regular content retrieval.

For information on filtering content during an export, see: Export-specific content filtering. For information on the Export to Word plugin, see: Export to Word.

Previously, the align left, center, and right toolbar buttons had no effect on an iframe inserted with the Page Embed plugin. Selecting the embedded iframe and choosing an alignment did not change its position.

In TinyMCE 8.7.0, the align left, center, and right toolbar buttons align an iframe inserted with the Page Embed plugin.

For information on the Page Embed plugin, see: Page Embed.

Previously, the Inline CSS plugin’s getContent API did not return a complete HTML document when the Full Page HTML plugin was enabled. The surrounding document header and footer were omitted, which made the output unsuitable for use cases such as generating email-ready documents.

In TinyMCE 8.7.0, the Inline CSS plugin detects when the Full Page HTML plugin is enabled and includes the document header and footer in its output. The getContent API now returns a full HTML document as expected.

For information on the Inline CSS plugin, see: Inline CSS.

Starting with TinyMCE 8.7.0, the TinyMCE AI plugin is available to self-hosted customers for the first time. Previously, the plugin could only be loaded from the Tiny Cloud CDN.

From this release, the tinymceai plugin is included in the tinymce-premium NPM package and is available as a standalone addon .zip download from the Tiny Account. The plugin is distributed only as an addon and is not included in any TinyMCE ZIP bundle.

A self-hosted plugin must still connect to an instance of the AI service. Point it at the hosted Tiny Cloud AI service, or deploy the self-hosted AI service to keep content within the host network. For installation steps, see: Quick start: TinyMCE from NPM or Yarn. For plugin configuration, see: TinyMCE AI.

Previously, previewing a quick action such as Translate showed a misaligned diff overlay when the editor body element used position: relative in a custom content_style. The overlay used the body element as its containing block instead of the viewport, but the positioning logic still used the viewport. As a result, the highlight cutouts appeared offset from the translated text. Print-style layouts and document templates that positioned the body element could make the preview difficult to use.

In TinyMCE 8.7.0, the diff overlay renders independently of the editor content styles. The overlay aligns with the translated text regardless of custom body positioning, and the cutouts highlight the active translated content as expected.

The TinyMCE AI plugin now supports the tinymceai_tool_data_callback option. This function runs when an MCP server sends an mcp-tool-result or mcp-tool-notification event during a streaming response. The function should return a string that would be displayed as the status message shown in the Chat sidebar while the AI model calls an MCP tool.

Previously, the text area in the Custom review section of the TinyMCE AI Review sidebar showed a scrollbar even when it was empty. The placeholder text could scroll and the corners of the text area appeared cut off, which made the control look broken.

In TinyMCE 8.7.0, the Custom review text area uses a larger default height, so the placeholder fits without a scrollbar and the text area renders correctly when empty.

Previously, the TinyMCE AI plugin logged a console warning when the tinymceai_default_model option was not set, even though omitting the option is valid. The warning suggested a misconfiguration and caused confusion.

In TinyMCE 8.7.0, the TinyMCE AI plugin no longer logs a console warning when the tinymceai_default_model option is not provided.

Previously, clicking a highlighted suggestion in preview mode in TinyMCE AI Chat and TinyMCE AI Quick Actions showed a selected state, even though preview mode offers no action for highlighted suggestions. The selected state made the suggestions appear interactive and led users to expect a follow-up action that preview mode does not provide.

In TinyMCE 8.7.0, highlighted suggestions in preview mode in TinyMCE AI Chat and TinyMCE AI Quick Actions do not respond to clicks and no longer show a selected state. The highlights remain visible for reference, so preview mode presents a read-only view of the final text.

Previously, the TinyMCE AI plugin set content into the editor without marking it as AI-generated. Integrations that listen to the BeforeSetContent and SetContent events had no reliable way to distinguish this content from content set by other sources, and could not apply origin-specific processing, tracking, or analytics.

In TinyMCE 8.7.0, the TinyMCE AI plugin adds an ai property to the BeforeSetContent and SetContent event payloads when it sets content. Event handlers can check this property to detect TinyMCE AI-generated content and respond based on its origin.

Previously, a user could not remove a context source from a TinyMCE AI conversation while the file was still uploading. A user who added a large file, such as an image or PDF, had to wait for the upload to the AI service to finish before removing it. The plugin provided no way to cancel a request that was already in progress.

In TinyMCE 8.7.0, the remove button on a context source now cancels an in-progress upload immediately. A user can remove a context source while it is still loading, without waiting for the request to complete.

Previously, Chat did not update an empty document when generating content. Chat displayed the generated content only in the Chat sidebar, because the AI service could not apply edits when the document had no content.

In TinyMCE 8.7.0, AI Chat can now handle updating an empty document. When the editor is empty, the generated content is now directly inserted into the document rather than only being displayed in the sidebar.

Previously, keyboard navigation in the Review sidebar did not match the Chat sidebar, so keyboard-only workflows behaved inconsistently when switching between the two sidebars. Pressing Esc could also reject all pending suggestions instead of moving focus, which meant keyboard users could discard suggestions unintentionally.

In TinyMCE 8.7.0, keyboard navigation in the Review sidebar matches the Chat sidebar. The Ctrl+Alt+S shortcut opens and focuses the Review sidebar. Tab and Shift+Tab move through the suggestion cards and the buttons on each card. Esc now moves focus instead of rejecting pending suggestions. Keyboard-only users can navigate and apply suggestions without a mouse.

TinyMCE 8.7.0 adds the tinymceai_reviews_change_tone_menu option for TinyMCE AI. This option controls which tone options appear in the Change Tone review and their order. Only preset tone IDs are supported. Duplicate IDs are removed, and the menu displays tones in the configured order. If the option includes an invalid tone ID, the configuration is rejected and the default tones are used. For valid tone IDs and option details, see tinymceai_reviews_change_tone_menu.

Previously, if the Review sidebar was hidden while the model was still responding and the resulting suggestions were then applied or skipped from the Preview footer, the review state was not reset. Reopening the Review sidebar showed "Review complete — no improvements found" instead of the review list, even though the review had finished. The only way to recover the review options was to reload the editor.

In TinyMCE 8.7.0, the review state now resets correctly after suggestions are applied or skipped from the Preview footer while the sidebar is hidden. Reopening the Review sidebar shows the review list again, so further reviews can be run without reloading the editor.

Previously, when the model unwrapped nested blocks into top-level blocks, such as converting <li> items into <p> paragraphs, it reused the original element IDs. The diffing logic treated the reused IDs as updates to the nested elements, so some prompts intermittently removed the content instead of unwrapping it. A reused ID is now treated as an existing block only when it points to a top-level element; otherwise it is processed as a new element. Edits that unwrap nested elements now apply reliably and preserve content.

Previously, a regression prevented earlier conversations from loading correctly in the Chat sidebar. After starting a new chat, returning to an earlier conversation and sending a prompt began a disconnected exchange instead of continuing the original thread. Switching to an existing conversation now restores its conversation ID, so later prompts continue the selected conversation.

Previously, images sent to the model were not uniquely identified, so a prompt referencing a specific image could mistake one image for another and apply changes, such as alt text updates, to the wrong image. TinyMCE AI now uniquely tags each img elements so they are less likely to be mistaken. Image edits now apply to the intended image, even when the content contains multiple images.

Previously, the Review sidebar supported only a fixed set of built-in reviews, selected by ID through the tinymceai_reviews option. There was no supported way for integrators to add named reviews, parameterized prompts, or menus that mixed built-in and custom reviews. Integrators had to rely on generic flows, such as Custom review, instead of dedicated review actions in the Review sidebar.

In TinyMCE 8.7.0, the tinymceai_reviews option also accepts integrator-defined review objects alongside the existing built-in string IDs. Integrators can define simple, list, and input review types, each with a custom name, description, and prompt. For the full schema and examples, see the tinymceai_reviews option.

Previously, when reviewing AI suggestions, the preview displayed both the deleted text and the inserted text side by side for replacements. This made the preview cluttered and harder to read, because the original and new content had to be parsed at the same time, especially when a document contained multiple replacements.

In TinyMCE 8.7.0, the preview hides the deleted text for replacements and shows only the new content. When a replacement is selected, the inserted content is shown and highlighted while the removed text stays hidden. Standalone deletions continue to show the removed text when selected, so pure deletions remain fully visible. This makes the preview cleaner and easier to read when reviewing AI-generated changes.

Previously, the AI suggestions preview rendered content inside a wrapper element within the preview iframe body, rather than directly into the iframe body as the editor does. Because the preview and editor had different structures, injected styles could render differently. Absolutely positioned elements and body-level CSS rules did not always apply the same way, which could cause glitches such as misaligned table headers and footers.

In TinyMCE 8.7.0, the preview inserts content directly into the iframe body so that its structure mirrors the editor. Injected styles now produce the same visual result in both, and the preview renders consistently with the editor.

Previously, when reviewing AI suggestions, the bulk action buttons always showed Skip remaining and Apply remaining, even before any suggestion had been applied or skipped. This was confusing because no decisions had been made yet.

In TinyMCE 8.7.0, the bulk action buttons reflect the current progress. They show Skip all and Apply all before the first decision, then switch to Skip remaining and Apply remaining after at least one suggestion has been applied or skipped. This behavior is consistent across the Chat and Quick Actions flows.

Previously, some tooltips in the TinyMCE AI interface were shown whenever their trigger condition was met, even when the content was already fully visible. This added unnecessary visual clutter.

In TinyMCE 8.7.0, these tooltips appear only when the content is truncated because it is too long to display in full. This reduces unnecessary tooltips and keeps the interface less cluttered.

Previously, user prompts shown in the AI Chat history collapsed consecutive spaces and line breaks. A multi-line prompt was displayed as a single run-on line, so the message in the chat thread did not match what was typed.

In TinyMCE 8.7.0, user prompts in the AI Chat history preserve their original line breaks and spacing, while long lines still wrap within the message. Prompts now display as they were typed.

Previously, the AI suggestion preview used icon-only accept and reject buttons, so the meaning of each action relied on the icon and its tooltip. This made the actions ambiguous and harder to discover.

In TinyMCE 8.7.0, the AI suggestion preview uses labeled buttons: a primary Apply button to accept a suggestion and a secondary Skip button to reject it. The clearer labels make each action obvious and improve accessibility.

Previously, after the AI Chat generated new content, resizing the browser window could leave the AI suggestions diff overlay misaligned with the underlying text. On some layouts the highlights became detached from the content they marked, which made the suggestions preview look broken.

In TinyMCE 8.7.0, the preview overlay tracks a wider set of size changes when the window is resized. The diff overlay now stays aligned with the generated content, which keeps the AI suggestions preview accurate.

Previously, the review suggestion cards in the AI Review sidebar used more padding than intended, which made the card layout look inconsistent with the design.

In TinyMCE 8.7.0, the spacing between the card header and body has been reduced to match the design. The review suggestion cards now have a more compact and consistent appearance.

Previously, when using the premium Snow skin, the AI suggestions preview overlay had a transparent background. The underlying editor content showed through the preview, which made it difficult to read and evaluate AI-generated suggestions.

In TinyMCE 8.7.0, the AI suggestions preview uses a solid white background in the Snow skin. Suggestions now appear on a clean, unobstructed background.

Previously, moving keyboard focus to the preview footer in the AI Chat always landed on the first view mode option rather than the one that was currently active. This made keyboard navigation between the Diff mode and Preview tabs less predictable.

In TinyMCE 8.7.0, focus moves to the currently active view mode in the preview footer. Keyboard navigation now reflects the active selection.

Previously, switching between the AI Chat and Review sidebars, or opening a sidebar during quick actions, while AI suggestions were still unresolved discarded those suggestions and any applied changes permanently. A single accidental click could cause lost progress.

In TinyMCE 8.7.0, a confirmation dialog appears before navigating away from unresolved suggestions. The action proceeds only after it is confirmed, which prevents the accidental loss of in-progress changes.

Previously, in Safari, hovering over text that was shortened with an ellipsis, such as AI Chat conversation titles or context sources, could display two tooltips at once: the browser’s native tooltip and the plugin’s custom tooltip.

In TinyMCE 8.7.0, only the native tooltip is shown for these elements in Safari. A single tooltip now appears on hover as expected.

Previously, aborting a streamed AI response and starting a new conversation could report an error. Aborting the response triggered a document delete operation that sometimes failed.

In TinyMCE 8.7.0, the document is no longer deleted when an AI request is aborted. Aborting a response and starting a new conversation no longer reports this error.

Previously, content shown in the AI preview was not filtered by the editor’s content rules until it was applied. With a strict schema configuration, a change could appear in the preview, be accepted, and then be removed when applied to the editor, so the final result did not match the preview.

In TinyMCE 8.7.0, AI response HTML is filtered through the editor’s content pipeline before it is shown in the preview. The preview now reflects what will be added to the editor, and if filtering removes all of the content the user is notified.

Previously, the state of an AI Chat conversation could be lost if the Chat sidebar was closed before the model began responding to a prompt. The plugin recorded which sidebar started a response only once the response began, so closing the sidebar beforehand left no record. Reopening the sidebar then reset the conversation and any pending preview.

In TinyMCE 8.7.0, the sidebar is recorded as soon as the prompt is sent. Closing and reopening the Chat sidebar before the response is ready no longer resets the conversation.

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