{productname} 8.4.0 was released for {enterpriseversion} and {cloudname} on Wednesday, February 4th, 2026. These release notes provide an overview of the changes for {productname} 8.4.0, including:
[[new-premium-plugin<s>]] == New Premium plugin<s>
The following new Premium plugin was released alongside {productname} 8.4.0.
The following premium plugin updates were released alongside {productname} 8.4.0.
The {productname} 8.4.0 release includes an accompanying release of the Media Optimizer premium plugin.
Media Optimizer includes the following addition.
Previously, SVG images could not be uploaded through the Media Optimizer plugin because Uploadcare placed restrictions on SVG file handling. Users who needed to include SVG graphics in content were unable to upload them directly.
In {productname} 8.4.0, SVG images can now be uploaded through the Media Optimizer plugin. Some CDN operations may have limitations on SVG files; for details, see the Uploadcare documentation on CDN operation limits.
For information on the Media Optimizer plugin, see: Media Optimizer.
The {productname} 8.4.0 release includes an accompanying release of the Full Page HTML premium plugin.
Full Page HTML includes the following update.
Previously, the Full Page HTML plugin used deprecated escape and unescape JavaScript APIs for some protected content handling. Those APIs are no longer recommended for new code.
In {productname} 8.4.0, the plugin uses modern encoding APIs instead. This aligns the implementation with current browser guidance and improves reliability for protected content handling.
A cross-site scripting (XSS) vulnerability was discovered in the Full Page HTML plugin. Previously, malicious code within the document <head> was able to be executed when pasted.
This vulnerability has been patched in {productname} 8.4.0 by ensuring that content in the document <head> is properly encoded.
New argument fullpagehtml to editor.getContent() and editor.setContent() APIs to only get/set the body of the content while the full page plugin is active.
Previously, setting and getting the editor content while the Full Page HTML plugin was active could be troublesome due to the presence of the full HTML document on all API calls, even when not needed. Attempting to get and act only on the body content (for example, for saving) was undocumented and required workarounds.
In {productname} 8.4.0, the fullpagehtml option has been added to the editor.getContent() and editor.setContent() APIs. When set to false, this option allows getting and setting only the body content while the Full Page HTML plugin is active, without interfering with the full document structure. The document is now more resistant to accidental changes, and content can be retrieved or updated without including the full HTML document. For details, see fullpagehtml option for getContent/setContent.
For information on the Full Page HTML plugin, see: Full Page HTML.
The {productname} 8.4.0 release includes an accompanying release of the Comments premium plugin.
Comments includes the following fix.
Previously, when creating or editing a comment in Comments, the save button could remain in a saving state indefinitely if the save operation failed or if the component was not replaced. The saving state had no way to reset to false except by recreating the component, which misled users into thinking the operation was still in progress.
In {productname} 8.4.0, the save logic now resets the saving state to false after the save operation completes, whether the operation succeeds or fails. The save button no longer remains stuck in a saving state.
For information on the Comments plugin, see: Comments.
The {productname} 8.4.0 release includes an accompanying release of the Suggested Edits premium plugin.
Suggested Edits includes the following improvement.
Previously, the document displayed in the Review Edits view relied on the deprecated browser method document.write, which could cause content to appear before it was fully styled. Users could briefly see partially rendered or unstyled content when opening the review interface.
In {productname} 8.4.0, the document loading process in the Review Edits view has been updated to remove the deprecated method. The document is now displayed only after it has fully loaded, improving browser compatibility and providing a smoother and more stable experience when reviewing suggested edits.
For information on the Suggested Edits plugin, see: Suggested Edits.
The {productname} 8.4.0 release includes an accompanying release of the Enhanced Skins & Icon Packs.
The Enhanced Skins & Icon Packs release includes the following updates:
The Enhanced Skins & Icon Packs were rebuilt to pull in the changes also incorporated into the default {productname} 8.4.0 skin, Oxide.
For information on using Enhanced Skins & Icon Packs, see: Enhanced Skins & Icon Packs.
{productname} 8.4.0 also includes the following addition<s>:
Previously, the noneditable plugin was converted to a feature in core in {productname} 6. The feature was always enabled with no documented way to turn it off, which was not always desirable for integrators.
In {productname} 8.4.0, a new allow_noneditable option is available. It is enabled by default. When set to false, the noneditable feature is disabled, equivalent to disabling the plugin prior to {productname} 6.
In {productname} 8.4.0, the new view_show option allows specifying which view to display when the editor is initialized. The option behaves similarly to sidebar_show but takes precedence for views; both sidebars and views can be configured to show on init.
{productname} 8.4.0 also includes the following bug fix<es>:
Previously, right-to-left (RTL) directionality was not correctly set for Hebrew in the language pack. This caused the editor to render the wrong directionality when Hebrew was set as the language.
In {productname} 8.4.0, this issue has been addressed by ensuring that the directionality is correctly set for Hebrew in the language pack.
Previously, when the editor content CSS was bundled, it was not loaded into preview iframes. This caused a visual mismatch between the editor content area and what users saw in the Preview dialog, Suggested Edits view and Revision History view.
In {productname} 8.4.0, the fix checks if the content CSS is available as a bundled resource and applies it to the Preview Iframe through style tags. Bundled content CSS is now correctly loaded in the Preview Iframe.