TinyMCE 6.0: Core changes

This section also includes four tables that set out the:

The following elements were previously deprecated and have, with this release, been removed entirely from TinyMCE.

The following elements were never documented and have never been formally supported.

Consequently, they were removed with this release without deprecation notices being provided in earlier releases.

The new editor.annotator.removeAll API replaces the removeAll method built-in to the Comments plugin.

The new editor.options API replaces two old APIs: editor.settings and editor.getParam.

Along with this new API, the new tinymce.activeEditor.options API replaces tinymce.activeEditor.settings.

The results returned from editor.uploadImages() API now include a removed property.

The property will be true when an image being uploaded is removed after failing to upload.

The new FakeClipboard API provides a means for storing state that can be set and accessed by plugins and the core editor.

FakeClipboard is implemented on the TinyMCE global, allowing anything to write to it and read from it.

The new Resource.unload API makes it possible to unload resources in the resource loader.

The dialog API’s setData method now uses a deep merge algorithm.

Consequently, it now supports partial nested objects.

Previously, the AddOnManager, PluginManager, ScriptLoader, StyleSheetLoader, and ThemeManager APIs reported resource loading status with success or failure callbacks.

These APIs now, instead, return a Promise. Also, EditorUpload, which already returns a Promise, had callbacks removed.

Previously, using closeButton to disable a Notification’s close button required a timeout value to also be set.

In TinyMCE 6, closeButton shows or hides the close button regardless of a timeout value being set or not set.

Equivalently, setting a timeout value sets how long the notification presents before automatically closing, regardless of whether a close button is displayed or not.

Previously, multiple TinyMCE APIs and UI components used disable or disabled in their method or property names.

In TinyMCE 6, these method and property names have been changed and configuration changes are required.

The toHex method has been removed from dom.DOMUtils.

The filterNode method has been removed from the DomParser API.

As well, the DomParser API no longer uses a custom parser internally and instead uses the native DOMParser API.

The content property of the SetContent editor event has been deprecated.

The following methods have been removed from the Env API:

Note, in particular, the removal of all legacy browser detection methods.

The fire() method in tinymce.Editor, tinymce.dom.EventUtils, tinymce.dom.DOMUtils, tinymce.util.Observable and tinymce.util.EventDispatcher has been renamed to dispatch().

fire has been aliased to dispatch, so existing integrations should still work as expected.

fire has also, however, been marked as deprecated. Using dispatch() in place of fire() is recommended.

Previously, editor.annotator.remove scrolled to the removed contents position when removing an annotation.

It did not, as expected, retain the current selection or insertion position in the TinyMCE editor.

With this release, editor.annotator.remove does not change the selection or insertion position after removing an annotation.

Previously, if the TinyMCE editor was removed, the editor.fire() API returned an incorrect object.

In TinyMCE 6.0, editor.fire(), which has been renamed dispatch(), returns the correct object even when the editor is removed.

The editor.getContent() API can now provide custom content by preventing and overriding content in the BeforeGetContent event.

This makes it consistent with the editor.selection.getContent() API.

The editor.setContent() API can also now be prevented from using the BeforeSetContent event.

This, too, makes it consistent with the editor.selection.setContent() API.

When the no_events argument is set to true, events should not fire when getContent is called. Previously, editor.selection.getContent() did not respect this.

In TinyMCE 6.0, editor.selection.getContent() treats the no_events setting as expected: when set to false, events are fired; when set to true, events are not fired.

The toHex method has been removed from html.Styles.

With all parsing moved to the DomParser API, the SaxParser API has been removed.

The table plugin’s functionality is, as of TinyMCE 6.0, entirely focussed on the user interface (UI) for creating and editing tables.

The code that generates tables is now a Core part of TinyMCE 6.0.

Since the table plugin API was entirely concerned with generating tables, it has been removed.

The tinymce.util.Promise API has been removed.

As part of moving the core autocompleter feature from the default silver theme to the TinyMCE core, two new commands are now available: mceAutocompleterClose and mceAutocompleterReload.

mceInsertTableDialog is the new command for invoking an Insert Table dialog.

The previous command, mceInsertTable, no longer works to invoke an Insert Table dialog: use the mceInsertTableDialog command instead.

The mceInsertTable command is still the command for inserting a table with specified properties directly and without asking for user input.

The Editor commands APIs no longer fallback to executing the browsers native command functionality.

As well, the Editor query command APIs now return false or an empty string on removed TinyMCE editors.

Previously, mceAddEditor and mceToggleEditor used the editorManager.settings values to set the id and UI and UX options for a new TinyMCE editor instance.

editorManager.settings is not used at all in TinyMCE 6 and has been removed.

Instead, the mceAddEditor and mceToggleEditor commands use id and options values from an object passed when the command is run.

The execCommand handler function has been removed from the plugin and theme interfaces.

The mceInsertRawHTML command has been removed.

As part of moving the core of the autocompleter feature from the default silver theme to the TinyMCE core, three new events are now available: AutocompleterStart, AutocompleterUpdate and AutocompleterEnd.

Themes can act on the AutocompleterStart and AutocompleterUpdate events and can call AutocompleterEnd to cancel the auto completer.

The BeforeSetContent event now includes the actual serialized content when passing in an AstNode to the editor.setContent() API.

The GetContent event now always passes a string for the content property.

A ThemeLoadError event is now fired if the theme fails to load.

The beforeinput event is expected to fire whenever content is added to or removed from a TinyMCE instance.

Previously, however, because of backspace and delete overrides in TinyMCE Core, the beforeinput event did not always fire when expected.

With this release, these overrides no longer prevent beforeinput events firing when expected.

Previously, the change event was triggered by the first modification made to a TinyMCE editor instance.

However, subsequent changes did not cause the event to fire until focus was switched away from the editor.

For example, typing a single character in to the TinyMCE editor text-entry area triggered the change event.

Consequent typing, or selecting of the entered character and modifying it by setting it to bold or italic, did not trigger further change events.

Making further modifications and then switching focus away from the editor did trigger this event, however.

As of TinyMCE 6, the change event is not fired unless and until

Previously the GetContent event did not fire when the editor.selection.getContent() API attempted to get tree or text formatted data.

With this release, the SetContent event fires as expected when editor.selection.setContent() attempts this.

The input event is expected to fire whenever content is deleted from a TinyMCE instance.

Previously, however, because of overrides in the DeleteBackspaceKeys.ts module, when more than one line was deleted, the input event did not fire.

With this release, these overrides no longer prevent an input event firing when multiple lines are deleted, as expected.

When a string is formatted as strikethrough, TinyMCE uses the <s></s> tag when the schema is HTML 5.

Also, given TinyMCE is now setting the HTML 5 schema by default, the default tag for the strikethrough format is the <s></s>, as is required by the HTML 5 schema.

Previously, element_format had no explicit default value. It’s implicit value, however, was 'xhtml'.

In TinyMCE 6.0, element_format now has an explicit default value: 'html'.

Previously the images_upload_handler option passed success or failure callbacks to report the status of an image upload.

In TinyMCE 6, images_upload_handler reports upload results by returning a Promise.

The link_default_protocol option sets the link protocol used by links added or edited using the link dialog.

It now defaults to 'https'. Previously it defaulted to 'http'.

Previously, the list of configured plugins could be retrieved by calling editor.getParam('plugins') and returned the configured plugins as a string.

As of TinyMCE 6, the list of configured plugins is retrieved by calling editor.options.get('plugins') and now returns the configured plugins as an array.

The textpattern_patterns option is no longer an option. It has been renamed to text_patterns and is now a Core part of TinyMCE 6.0.

All references to textpattern_patterns should be changed to text_patterns.

Also, text patterns are now on by default: text_patterns: false turns the functionality off.

With the removal of the, now deprecated, toHex APIs, RGB colors are no longer converted to hex values when parsing or serializing content.

Enhanced Image Editing, a Premium plugin, replaces the now-deprecated and removed ImageTools plugin. The imagetools plugin is no longer part of the Core open source editor.

The following editimage options replace the old imagetools options:

editimage also offers a new option: editimage_proxy_service_url. This option has been added as a new recommended method when using Tiny services.

The emoticon plugin now uses the more accurate word, Emoji, in its toolbar, menu item and dialog.

In previous versions, the word presented in these parts of the plugin’s user-interface was Emoticon.

There are no end-user facing changes between the previous toc plugin and the tableofcontents plugin.

The following Premium Plugins now present in Hindi, Malay, and Vietnamese:

Previously, the autoresize plugin offered an autoresize_on_init option.

This setting does not do anything meaningful, and had been previously deprecated.

As of TinyMCE 6.0, autoresize_on_init has been removed from the autoresize plugin.

In TinyMCE 5.x, the media plugin used SaxParser to validate elements for parsing.

As of TinyMCE 6.0, SaxParser is no longer used. Another TinyMCE public API — DomParser — is used instead.

As a consequence the iframe, video, audio, and object elements are no longer marked as special. Instead their contents are simply validated against the TinyMCE schema.

Also, the media plugin’s media_scripts option was deprecated in TinyMCE 5.10.

As of the release of TinyMCE 6.0, this option has been removed completely.

The noneditable plugin is no longer a plugin. It is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to noneditable should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

The paste plugin’s functionality is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to paste should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

The paste_data_images option now defaults to true. When paste was a plugin, this option was, by default, set to false, which prevented images being pasted from the local machine.

The mceInsertClipboardContent argument, content, has been renamed. It is now html.

The new name is a more accurate reflection of what sort of data the argument passes.

print functionality is no longer a plugin. It is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to print should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

The table plugin’s functionality is, as of TinyMCE 6.0, entirely focussed on the user interface (UI) for creating and editing tables.

The code that generates tables is now a Core part of TinyMCE 6.0.

This, now core feature of TinyMCE 6.0, also includes the following fixes, changes, and improvements.

As per the previous TinyMCE 5 announcement, the bbcode plugin has been removed. It is no longer part of TinyMCE 6.0. And it is not otherwise available.

Color Picker’s functionality has been a built in part of TinyMCE since version 5.

Consequently, and as per the previous TinyMCE 5 announcement, the empty colorpicker plugin has been removed.

Context Menu’s functionality has been a built in part of TinyMCE since version 5.

Consequently, and as per the previous TinyMCE 5 announcement, the empty contextmenu plugin has been removed.

As per the previous TinyMCE 5 announcement, the fullpage plugin has been removed. It is no longer part of TinyMCE 6.0. And it is not otherwise available.

The hr (horizontal rule) functionality is no longer a plugin. It is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to hr should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

The imagetools plugin is no longer part of the Free TinyMCE editor. Image Tools is now Enhanced Image Editing, a Premium plugin.

As per the previous TinyMCE 5 announcement, the legacyoutput plugin has been removed. It is no longer part of TinyMCE 6.0. And it is not otherwise available.

The paste functionality is no longer a plugin. It is now a Core part of TinyMCE 6.0.

Because the functionality was unmaintainable, paste no longer supports input from Microsoft Word.

There is an open request for maintainers should someone in the community be interested in taking over maintenance of this particular functionality as a separate plugin.

If a community-maintained version of the paste plugin becomes available, we will link to it from the Migration Guide.

print functionality is no longer a plugin. It is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to print should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

As per the previous TinyMCE 5 announcement, the spellchecker plugin has been removed. It is no longer part of TinyMCE 6.0.

The Premium plugin, Spell Checker Pro, which offers equivalent functionality and more, is available.

The tabfocus plugin has been removed. It is no longer part of TinyMCE 6.0. And it is not otherwise available.

The tabfocus_elements option, which relied on the tabfocus plugin, no longer functions.

As well, the tab_focus option was previously deprecated by tabfocus_elements. With this release, the tab_focus option has been removed completely.

As per standard web practice, the tabindex attribute should be used instead of the tabfocus plugin or any of the tabfocus plugin’s options.

As per that standard web practice, the tabindex attribute is copied from the target element to the iframe.

The toc plugin is no longer part of the Core open source editor. Table of Contents is now a Premium plugin.

Text color’s functionality has been a built in part of TinyMCE since version 5.

Consequently, and as per the previous TinyMCE 5 announcement, the empty textcolor plugin has now been removed.

The textpattern functionality is no longer a plugin. It is now a Core part of TinyMCE 6.0.

In TinyMCE 6.0, there is no setting or specifying this functionality in the plugins option.

All references to textpattern should be removed from your plugin configuration. Leaving references to removed plugins in a plugin configuration will cause console errors documenting the plugin failing to load.

When a TinyMCE editor instance was ended, the global setting, tinymce.settings, which is set at editor initialisation, retained references to DOM elements from the no-longer extant editor instance.

With this release, tinymce.settings is no longer set at editor initialisation and has subsequently been removed.

The editor.settings property has been replaced by the Options API.

It has, consequently, been removed from TinyMCE 6.0.

The fixed property has been removed from the tinymce.html.Node class.

The shortEnded property has been removed from the tinymce.html.Node class.

The assignment operator character — : — has been changed to ~ for the valid_elements and extended_valid_elements schemata.

The : is also used to assign a [xlink:href] rule and this was not possible in these schemata because the colon character was acting as an assignment operator.

This change allows both schemata to set attribute values for the valid_elements and extended_valid_elements options using the ~ character and assign [xlink:href] rules as expected.

The TinyMCE color picker presents tooltip labels showing the name of the color the pointer is hovering over.

These labels presented these names in English in multiple instances when they should have presented the names in other languages (eg German).

With this update, these tooltip labels now present in the expected language.

buttonType is a new property available for button components used in dialogs.

It replaces the, now deprecated property, primary.

The primary property was boolean, allowing for only two states: true and false.

The new buttonType property can take any of three states: 'primary', 'secondary', and 'toolbar'.

Setting buttonType: 'primary' is the same as setting primary: true.

Setting buttonType: 'secondary' is the same as setting primary: false.

Previously, when a component in a TinyMCE dialog changed — for example, when a next or previous button was clicked — the entire dialog was re-rendered.

In TinyMCE 6.0, the initialData type is now Partial<T>, which matches the underlying implementation.

And, relatedly, the redial API now re-renders only the portions of a dialog that have changed.

The Format Painter toolbar item now has a matching menu item.

The dialog API’s setData method now uses a deep merge algorithm.

Consequently, it now supports partial nested objects.

In TinyMCE 5.x, editors without a height value specified in the TinyMCE configuration defaulted to a 200px high editor.

In TinyMCE 6.0, editors without a height value specified in the TinyMCE configuration default to a 400px high editor.

As was the case in TinyMCE 5.x, this new default only applies to editors in iframe mode, not inline mode.

Also, editors now have a min-height default value of 100px. This prevents the editor UI from disappearing during re-sizing, which prevented users from interacting with the editor.

Previously, when a theme was requested, TinyMCE downloaded it completely before fetching accompanying components, such as icons, plugins, and language packs.

With this release, when a theme is called, related components are downloaded in parallel with the theme.

The new imagepreview dialog component allows for previewing and zooming of any image URL.

Clicking on or near the boundaries between editable and noneditable elements (eg in the padding of a noneditable element containing an editable element), there are established and expected norms as to where the insertion point should present after the click.

With this release, TinyMCE has improved the placing of the insertion point on either side of a noneditable element when clicking on or near these boundaries.

TinyMCE 6.0 includes a new slider dialog component.

buttonType is a new property available as a basic panel component of dialogs.

It replaces the, now deprecated property, primary.

Previously, TinyMCE UI classes provided a .disabled property.

In TinyMCE 6, this property has been renamed to .enabled.

Also, the Dialog API, which previously offered the disable(<name>) and enable(<name>) functions, now offers a single setEnabled(<name>, <state>) function.

The Powered by Tiny text string set in the TinyMCE status bar is now the TinyMCE logo.

The default status bar path delimiter character (also known as a breadcrumb separator) has been changed.

It was » (the double, right-pointing, angled quotation mark).

It is now › (the single, right-pointing, angled quotation mark).

When allow_html_in_named_anchor was set to true, content inside the anchor element was wrapped such that each character was set on a new line.

With this release, setting allow_html_in_named_anchor: true sets characters inside the anchor element as entered, with no wrapping of each character to a new line.

Previously, TinyMCE’s default UI theme, silver, was initialised such that it rendered some UI components before plugins that, potentially, would override or adjust the defaults presented by silver.

This resulted in these UI elements rendering incorrectly.

With this release, silver no longer renders these UI elements before plugins get to override or adjust, and these components no longer render incorrectly.

Previously, TinyMCE dialog labels and other UI elements were rendered with HTML markup.

With this release, the text and label properties of these elements are now rendered as plain text, as expected.

Calls to editor.selection.setRng now update the insertion point bookmark when focus is returned to the editor.

For the end-user, this change means content dragged from outside the TinyMCE editor into the editable area will be placed into the TinyMCE document where the insertion point appears as the drag is completed.

This is the expected behavior.

Previously, in Google Chrome 93 and later, navigating through TinyMCE menus using the keyboard did not cause screen readers to read out menu items.

This has been corrected with this release.

Screen readers now read menu items as the TinyMCE menus are traversed, as expected.

The text on some buttons and menu items incorrectly presented in Title Case.

The underlying strings have been corrected and these items now present in sentence case, as expected.

The mobile theme was deprecated when integrated support for mobile devices was added to the silver theme.

The mobile theme has been removed.

The primary property was a boolean property available for button components used in dialogs

It has been deprecated and replaced by the new buttonType property.

The Style field, previously presented in the Advanced tab of the Insert/Edit Image dialog has been removed.

When the Advanced tab in the Insert/Edit Image dialog was selected, a Style text-entry field (auto-populated with the selected image’s properties and associated values) was one of the fields presented.

A bug in TinyMCE prevented the field from being edited, however.

Separate from the text-entry bug, supporting edits in this field properly is out-of-scope for this release of TinyMCE.

An internal feature request to re-implement this feature when it can be done so safely has been logged.

Pressing the End key when the insertion point is somewhere in a line of editable text should move the insertion point to the end of that line.

In the previous release of TinyMCE, pressing this key moved the insertion point outside the element containing the editable text entirely.

As of this TinyMCE release, pressing the End key when the insertion point is in a line of editable text moves the insertion point to the end of that line, as expected.