TinyMCE 6.5.1

The new Open Source plugin, Accordion allows for the creation of sections in a document that can be expanded or collapsed to show or hide additional content.

The Accordion plugin also provides integrators with four commands:

and two initialization options

For information on the Accordion plugin see Accordion.

The TinyMCE 6.5.1 release includes an accompanying release of the Enhanced Media Embed premium plugin.

Enhanced Media Embed 3.1.2 includes the following fix.

The TinyMCE 6.5.1 release includes an accompanying release of the Case Change premium plugin.

Case Change 2.0.2 includes the following change.

Previously, the Case Change plugin could change the case of a selection inside an element with a contenteditable="false" attribute set.

In Case Change 2.0.2, the Case Change toolbar button and menu items are disabled when the selection is in an element with a contenteditable="false" attribute set.

For information on the Case Change plugin, see: Case Change.

The TinyMCE 6.5.1 release includes an accompanying release of the Checklist premium plugin.

Checklist 2.0.5 includes one fix:

The TinyMCE 6.5.1 release includes an accompanying release of the Link Checker Premium plugin.

Link Checker 3.0.3 includes one fix:

The TinyMCE 6.5.1 release includes an accompanying release of the Accessibility Checker premium plugin.

Accessibility Checker 3.2.0 includes the following fix, and improvement.

The TinyMCE 6.5.1 release includes an accompanying release of the Advanced Code Editor premium plugin.

Advanced Code Editor 3.3.0 includes the following three changes, and one fix:

The TinyMCE 6.5.1 release includes an accompanying release of the Spell Checker Pro premium plugin.

Spell Checker Pro 3.3.0 includes three additions and one change:

The TinyMCE 6.5.1 release includes an accompanying release of the Advanced Templates premium plugin.

Advanced Templates 1.2.0 includes one improvement, one addition, and four fixes:

The TinyMCE 6.5.1 release includes an accompanying release of the Merge Tags premium plugin.

Merge Tags 1.3.0 includes three fixes:

The TinyMCE 6.5.1 release includes an accompanying release of the Advanced Typography premium plugin.

Advanced Typography 1.1.2 includes three fixes:

The TinyMCE 6.5.1 release includes an accompanying release of the Power Paste premium plugin.

PowerPaste 6.2.0 includes two fixes:

In previous versions of TinyMCE, an issue related to the a:link selector in the CSS received from Microsoft Word was identified.

When content containing links was pasted from a Microsoft Word file into a TinyMCE instance running the PowerPaste plugin, the pasted-in link text rendered using the Times New Roman font family. And it presented thus no matter the typeface set for this text in the original Microsoft Word document.

To work around this, TinyMCE 6.5.1 removes the default CSS styling applied by Microsoft Word during the paste operation.

With this change, link text copied from Microsoft Word using the PowerPaste plugin now uses the font-family matching that used in the source document.

For information on the PowerPaste plugin, see: Introduction to PowerPaste.

The TinyMCE 6.5.1 release includes an accompanying release of the Format Painter Premium plugin.

Format Painter 2.0.2 includes one fix:

TinyMCE’s Real-time Collaboration (RTC) plugin will be deactivated on December 31, 2023, and is no longer available for purchase.

The Premium Skins and Icon Packs release includes the following updates:

The Premium Skins and Icon Packs were rebuilt to pull in the changes also incorporated into the default TinyMCE 6.5.1 skin, Oxide.

For information on using premium skins and icon packs, see: Premium Skins and Icon Packs.

Previously it was mandatory for the DialogFooterToggleButton to have an icon prop.

Toggle buttons in dialog footers did not function without a displayed icon.

As of TinyMCE 6.5.1 the icon prop is now optional and toggle buttons in dialog footers work with and without a displayed icon.

In previous versions of TinyMCE, translations for the text on the “Keyboard Navigation” tab in the Help dialog were not available due to a flaw with the way translations were delivered.

Conventionally, translations were parsed into JavaScript files containing objects which were keyed by the English string, with the value being the translated equivalent in a different language. This was unsuitable for very long strings such as the text on the Keyboard Navigation tab.

In TinyMCE 6.5.1, a new pipeline has been implemented for delivering translations of long strings. Professional translations of text within the Keyboard Navigation tab inside the Help dialog have also been procured.

As a result, the text in the Help dialog’s Keyboard Navigation tab is now shown in the language specified by the current editor’s language option.

When using voice assistant software in previous versions of TinyMCE, focusing on the editor resize handle would not announce any instruction.

In TinyMCE 6.5.1, instructions for using arrow keys to adjust the editor viewport’s size are now announced upon focusing the editor resize handle, while using voice assistant software.

When multiple table cell elements are selected, by default, a blue background indicates their selection.

In previous TinyMCE versions, however, once a cell selection was made, the Quickbar toolbar presented as pointing at the contents of the last cell in the selection. This gave the (incorrect) visual impression that formatting changes would only affect the contents of cell.

In TinyMCE 6.5.1, when multiple table cells are selected, the Quickbar plugin calculates the bounding box of the selected cells. Using this information, the Quickbar now presents with the toolbar’s pointer directed at either the middle or the beginning of the selection, considered horizontally.

This presentation makes it clearer that any Quickbar buttons will be applied to the entire selection.

In previous versions of TinyMCE, a toolbar flicker was identified when editor instances are re-initialized.

As an option to reduce this, TinyMCE 6.5.1 includes a new setting, init_content_sync.

This option allows the editor iframe to be initialized using document.write instead of srcdoc, resulting in a synchronous initialization process that reduces toolbar flicker.

In previous versions of TinyMCE, when a table was copied and pasted inside an existing table, the content of the copied table would fill the existing table instead of being pasted as a whole inside the table cell where the paste was performed.

TinyMCE 6.5.1 includes the new option, table_merge_content_on_paste, that allows for this behavior to be turned off.

When this option is set to false table merging is disabled and the pasted-in table is inserted into the desired table cell during the paste operation instead.

Dragging and dropping elements with a contenteditable="false" attribute within TinyMCE emits dragstart, drop, and dragend events as expected.

However, in previous versions of TinyMCE, these drag events had their dataTransfer property set to null. According to web standards it should be set to a DataTransfer object holding the drag operation’s data.

As a consequence, integrators were unable to view and manipulate the HTML drag data in these drag events.

In TinyMCE 6.5.1, dragstart, drop, and dragend events now have their dataTransfer property populated with a DataTransfer object whose text/html data holds the outerHTML of the contenteditable="false" element being dragged.

Additionally, a custom mode module has been implemented to ensure that the DataTransfer object is in read-write mode in dragstart events, read-only mode in drop events, and protected mode in dragend events, as per standard.

In previous versions of TinyMCE, an issue was identified where toolbar and menu items were not presenting as disabled when the contents of elements with a contenteditable="false" attribute were selected from inside a editor root with a contenteditable="false" attribute set.

In this circumstance, toolbar buttons and menu items appeared as enabled even though the buttons and menu items were in a disabled state based on the user’s current selection.

TinyMCE 6.5.1 now explicitly disables toolbar buttons and menu items based on the user’s selection.

In addition, if the contents of elements with a contenteditable="true" attribute are selected in the same circumstance, the toolbars and menu items are re-enabled.

For TinyMCE 6.5.1, improvements were made to the tabpanel dialogs: labels on the tabs can now wrap to multiple lines. This improves the readability of the tab labels, particularly when longer labels are displayed.

In particular, the keyboard navigation text in the help dialog is now readable in all languages, without compromising the width of the dialog tab buttons.

In previous versions of TinyMCE, an issue was identified that prevented unlisted Vimeo videos from been added to the editor when using the Media plugin.

The Media plugin failed to correctly insert the video into the content due to TinyMCE ignoring the h parameter when parsing the source URL.

In TinyMCE 6.5.1, the h parameter is now parsed and included in the source URL by TinyMCE.

As a result, embedding unlisted Vimeo videos into a TinyMCE editor using the Media plugin now works as expected.

During the TinyMCE 5.x lifetime, browser-native select form elements were replaced by a TinyMCE native dropdown component. However, some browser-native select form elements were not replaced by the custom dropdown component.

This caused inconsistent user interface as certain parts of the application continued to use the browser-native selectbox. Affected components include the Advanced Code, Template, Accessibility Checker, Page embed, Permanent Pen, and Advanced Table plugins.

With the release of TinyMCE 6.5.1, all form select elements now use the TinyMCE native select component, listbox, instead of the browser-native selectbox. This change ensures a consistent user interface throughout TinyMCE.

A change was made in TinyMCE 6.4 that caused the help dialog to become narrower.

As a result, users experienced difficulty in reading the content, especially in languages other than English.

To address this issue, the width of the help dialog has been restored to its previous size, ensuring better readability for all users.

For example, the URL text-entry field in the Link dialog is a combobox. When this element is focused with a screen reader, it is announced as a combobox and pressing the down arrow shows the available list items.

In previous versions of TinyMCE, however, none of these items were announced by the screen reader as they were selected, making these items effectively invisible to screen reader users.

With this update, listed items in a combobox can be announced by screen readers, as expected.

Previously, when dragging and dropping image elements within the editor, the dragend event would, in some circumstances, not trigger when the host browser was Mozilla Firefox.

With this update, a fix for this was implemented. TinyMCE 6.5.1 now ensures that the dragend event consistently fires when an image is dropped in the editor, even when the host browser is Firefox.

In previous versions of TinyMCE, the anchor element — <a> — could have block elements added as children when the schema was set to HTML 4.

Consequently, applying a heading element (for example, an <h1> element) to a link within a table caption would affect the editor view, even though the table caption tag was not included in the serialized content.

To address this issue, an update was made to the editor’s HTML4 schema: block child elements are now not allowed in anchor tags.

As a result, applying block formatting to link content in TinyMCE 6.5.1, should no longer have any impact.

In previous versions of TinyMCE, the <caption>, <dt> and <address> elements could have block elements added as children when the schema was set to HTML 4.

The HTML 4 schema does not support this and, as a consequence, TinyMCE documents containing such child elements did not validate against HTML 4-specific parsers and validators.

In TinyMCE 6.5.1, the editor’s HTML 4 schema has been corrected. Block elements are now, correctly, considered invalid inside such elements and are automatically unwrapped out of the elements noted above.

Previously, when a file containing adjacent anchor element around block element structures was added to the root of a TinyMCE editor instance, the whitespace between each anchor-block structure was, incorrectly, turned into an empty paragraph.

This update corrects this. When such structures are inserted into a TinyMCE 6.5.1 instance, the extra paragraph is no longer inserted between the block elements.

Previously, if the TinyMCE root element had a contenteditable="false" attribute set and the unlink editor command was used while a link was selected, the link was, incorrectly, removed.

For this update, the unlink command was updated. If the current selection is within an element with a contenteditable="false" attribute set, issuing an unlink command has no effect: the link remains in place as expected.

In previous versions of TinyMCE, certain toolbar items did not render the ‘unavailable’ mouse pointer when the toolbar item was unavailable. This occurred when the text color and fontsizeinput controls were rendered in a disabled toolbar.

As a result, the disabled state of these toolbar items was not correctly shown.

In TinyMCE 6.5.1, the CSS was modified to provide clearer visual indications for disabled toolbar items. As a result, the toolbar items are now properly disabled, appearing greyed out and displaying an unavailable mouse pointer.

If the selection is in an element with a contenteditable="false" attribute set, and spot-formatting is applied to the selection, the spot formatting is not applied to the selected content, as expected.

However, In previous versions of TinyMCE, in such a circumstance, the spot formatting was erroneously applied to the nearest writeable element, if such an element existed.

This incorrect application of spot-formatting also presented when the formatter API was used, because the API’s canApply function did not return false when the selection was in an element with a contenteditable="false" attribute set.

In TinyMCE 6.5.1, the issue has been resolved. Spot formatting is no longer misapplied to not-selected elements.

Previously, text directionality commands, which set the dir attribute, could be applied to elements with a contenteditable="false" attribute set when those elements were within a root with a contenteditable="false" attribute set.

As of this release, TinyMCE now checks if a selected element has a contenteditable="false" attribute set. And, on elements with this attribute set, text directionality commands are not applied to the selection, as expected.

Previously, when a TinyMCE document had an inline element with a contenteditable="false" attribute set inside a block element that had a text direction of right-to-left, the insertion point would move in the wrong direction when traversing the inline element using arrow keys.

As of this release, when such an inline element, inside a block element with a right-to-left text direction, is traversed, TinyMCE moves the insertion point in reverse logical order.

This ensures the insertion point traverses the inline element as expected, moving over the element in the direction expected by the arrow-key being pressed.

Previously, when the document root had a contenteditable="false" attribute set, the Quickbar toolbar appeared when an element with its own contenteditable="false" attribute was selected.

A fix was applied to the Quickbar toolbar in TinyMCE 6.5.1. The toolbar now sets itself to hidden if the current selection is within an element with a contenteditable="false" attribute set.

In previous versions of TinyMCE, the table toolbar remained visible even if the table was within a host element that had the contenteditable="false" attribute set, making the Table read-only, and making the visible Table toolbar unhelpful, at best.

In TinyMCE 6.5.1, this issue has been resolved. The editor no longer shows the Table toolbar when the selection is within a host element that has the contenteditable="false" attribute set.

Previously, the dialog’s body content was setup with a maximum height of 650px (max-height: 650px;).

As a consequence, scrolling was only enabled in dialog’s when the dialog’s content exceeded this height. As a further consequence, when dialogs were less than 650px high, the dialog’s footer could extend below the dialog’s bounds, putting the controls in the footer out of view. This particularly presented in dialogs that do not have tabs.

In TinyMCE 6.5.1, the dialog body’s max-height is set to a calculated value: the minimum value between 650px and the viewport height (vh) minus 110px. 110px, here, is the combined height of a TinyMCE dialog’s header and footer.

TinyMCE dialogs now display consistently and correctly. And footer controls appear in view.

When determining an element’s directionality, the direction style takes precedence over the dir attribute in many cases.

However, in previous versions of TinyMCE, the Directionality plugin only affected the dir attribute and did not consider any direction style, whether inline or from a stylesheet. Consequently, the Directionality plugin did not visually affect elements with a CSS direction style applied.

As of TinyMCE 6.5.1, the Directionality plugin takes into account the direction CSS style while still giving priority to the dir attribute.

In TinyMCE 6.5.1, when Directionality is applied to an element:

The final step above — the addition of an inline direction CSS style — most often occurs if the element derives a different direction style from a stylesheet.

As a consequence of these changes, the Directionality plugin now functions as expected for elements with a direction CSS style applied.

Previously, in Safari running on iOS, when a newline was inserted (by pressing the Enter key) and the user continued typing without moving the insertion point, the characters typed on the newline merged onto the previous line and the newline was removed.

This occurred because Safari on iOS composes Hangul syllabic blocks by deleting the individual jaso glyphs and inserting the expected block glyph, continuing until a browser-native Enter keypress event is fired.

However, TinyMCE has its own Enter key handler on keydown. In this circumstance, therefore, the native keypress event was suppressed. This caused Safari on iOS to continue composing the syllabic block across the newline by firing a deleteContentBackward input event to delete the newline and then inserting the block on the previous line.

For TinyMCE 6.5.1, when the user is in Safari on iOS and the insertion point is detected as positioned after a Korean character, on Enter key keydown;

This prompts Safari on iOS to end the syllabic block creation session for the previous character.

Then, on the Enter key keyup event;

This ensures that, when running in Safari on iOS, Safari no longer attempts to compose syllabic blocks across newlines, preventing the unwanted behavior from occurring.

Previously, Word Count treated some characters as separate words rather than as part of the word they were connected to. The following characters specifically:

This resulted in inaccurate word counts.

In TinyMCE 6.5.1, Word Count’s Unicode punctuation string has been updated to include these characters as exceptions. By doing so, the updated function more accurately count words, including the previously mishandled characters, providing a more reliable word count.

On systems running macOS, the Command+Delete (⌘+Delete) keyboard shortcut deletes the material from the insertion point to the beginning of the line. Previously, however, when this shortcut was used in a TinyMCE instance, the expected undo level was not registered.

A workaround did exist. If a further action was taken (eg text was entered or the Delete key was pressed to remove another character) the new action and the ⌘+Delete action were both added to the undo stack.

With this update, the TinyMCE editor now registers an undo level when the ⌘+Delete shortcut is used, allowing end-users to undo the action immediately (by, for example, pressing ⌘+Z) and without having to add a further action.

On systems running Windows, the Ctrl+Delete keyboard shortcut deletes all characters to the left of the insertion point, up to the next word boundary and the Ctrl+Backspace keyboard shortcut deletes all characters to the right of the insertion point, up to the next word boundary.

In previous versions of TinyMCE, however, if either the ctrl+delete or ctrl+backspace keyboard shortcut was used and immediately followed by an undo or redo operation, the insertion point was re-set incorrectly (often, but not always, at the beginning of the line affected by the operations).

This issue was resolved for this release: using either the ctrl+delete or ctrl+backspace keyboard shortcut and an undo or redo operation in turn now sees the insertion point placed correctly, as expected.

In previous versions of TinyMCE, if the insertion point was set between two image elements and the backspace key was pressed, the trailing image was mistakenly treated as an inline formatting element that should be deleted

Consequently, the image after the insertion point was deleted, not the image before the insertion point.

With this update, TinyMCE now determines the element structure properly and no longer treats the trailing image incorrectly.

Pressing the Backspace key in this circumstance now deletes the image before the insertion point, as expected.

Previously, issues between the host browser and the editor switching between an element’s children, lead to the element presenting an erroneous empty state when displayed.

To resolve this, such elements can no longer be empty unless the user explicitly sets them as such.

In TinyMCE 6.5.1, these elements will now have a populated value unless the user specifically chooses an empty selection.

Previously, resize handles presented on tables in a newly-initialized editor even though the table did not have focus. This happened because the insertion point is automatically placed in the first valid element (in this case, a table cell) during editor initialization.

In TinyMCE 6.5.1, the resize handles have been adjusted to prevent their display when the insertion point is inside a table element without the editor being focused.

In the previous version of TinyMCE, the checkbox element’s disabled state was not correctly applied to all elements. As a result, the state was neither properly removed nor added as intended.

This error also left checkboxes potentially presenting as in a state that was not true (for example, presenting as enabled when they were not enabled).

To rectify this issue, the control was adjusted and relocated to ensure that it functions as expected.

With this update, enabling or disabling checkboxes sets the correct classes and attributes and presents the current state correctly to the end-user.

Previously, the Find and Replace dialog was not updated following a modification to the “Find in selection” option. Consequently, the “not found” alert would persist and not disappear as intended.

To resolve this issue, necessary UI updates were implemented after the change to the “Find in selection” option. As a result, the “not found” alert is now reset every time the “Find in selection” option is altered.

Previously, when an image upload into an otherwise empty paragraph failed, the upload failure resulted in the empty paragraph not having the expected <br> tag to serve as padding.

When the upload failure was noted by a TinyMCE editor instance, and the placeholder material for the expected image was removed by the editor, the expected padding was not set.

The empty paragraph element was, in this circumstance, rendered inaccessible. And it presented to the end-user as the empty paragraph element being removed or improperly formatted.

In TinyMCE 6.5.1, when the images_upload_handler gets a remove: true callback, the parent element is checked and, if required padding is not present, it is added.

Previously, when Google Chrome was the host browser, there were circumstances where adding a newline character after a table did not produce the expected outcome (that is, a new line).

When the insertion point was positioned after a table, it was placed in the <body> at offset 1 instead of within any of its children.

As a result, when an element with a contenteditable="false" attribute came after it, it was deemed invalid to insert a newline at that position. Consequently, no newline was added.

As of this release, TinyMCE now recognizes this position as valid, and the expected root blocks are inserted.

There was an issue with exiting a blockquote element when the insertion point was positioned at the end of the element. This issue arose because, when inserting a new block, the check to determine if the block is empty treated nodes containing a zero-width space (ZWSP) as non-empty.

As part of this update, TinyMCE 6.5.1 now correctly recognizes elements containing a ZWSP as empty blocks.

As a consequence, exiting blockquote elements now happens even when the insertion point is at the end of the element, as expected.

In previous versions of TinyMCE, a presentation issue was caused by a discrepancy between the setup handler for the Advanced List — advlist — Quickbar button in the advlist Premium plugin and the setup handler for the List — list — Open Source plugin.

Consequently, the status of the advlist Quickbar button was not updated correctly during setup.

To resolve this, the setup handler for the advlist plugin was aligned with the one used in the list plugin. The status of the buttons is now accurately rendered, as expected.

In previous versions of TinyMCE, an issue was identified that resulted in the incorrect execution of the remove_trailing_br function by DomParser. This resulted in the insertion point focusing on the <tr> element instead of the <td> element.

As a consequence, when inserting a table with the focus on <tr>, the table would be placed in the wrong location.

To fix this, the remove_trailing_br function was extracted, with the default behavior now set to execute within the serializer. Although the function remains in the parser, its default setting has been modified to not execute by default, as removing it entirely could cause compatibility issues.

When users seek to move a template to another category, a Move to… dialog is presented, with a dropdown list of available categories.

In previous versions of TinyMCE, this list included a redundant category: the current category of the template being moved. If the selected destination category in the Move to… dialog matched this original template category, the operation had no effect.

In TinyMCE 6.5.1, the destination category list now filters out the category of the template being moved.

Consequently, users no longer see the parent category of the template in the Move to… dialog’s category list.

In Safari running on macOS, when a dialog was closed by clicking outside the dialog, a bug caused the browser to select the active element and scroll down.

This caused the browser to scroll the viewport to the bottom of the dialog after the dialog closed.

This scrolling did not occur if the dialog was closed by pressing the dialog close control or by typing the Esc key.

To fix this issue, TinyMCE now forces the active element to blur when Safari is the host browser. By doing so, no element is selected after closing the dialog, preventing the unintended scrolling behavior.

In previous versions of TinyMCE, an issue was identified in the close buttons: invalid markup was present. Specifically, a div element was being used within the buttons. This violates HTML standards and caused problems when running TinyMCE HTML through markup checkers: the checker, correctly, threw errors.

In TinyMCE 6.5.1, the markup was fixed by replacing the div element with a <span> element, aligning it with HTML guidelines. As a result, the updated close buttons now pass HTML markup checkers without throwing errors.

When using voice assistance software in previous versions of TinyMCE, whenever an interactive dialog was opened, the voice assistant would announce each label consecutively in the dialog.

In TinyMCE 6.5.1, voice assistant software no longer announces the entire content of the dialog body, meaning only the focused interactive element will be announced when first opened.

In previous versions of TinyMCE, a bug was identified that affected the constrained bound calculations for toolbar dismissals, when the toolbar_location: 'bottom' option was set.

As a consequence, when this configuration was used within a scrollable container, scrolling downwards would result in the premature dismissal of the toolbar, before reaching the bottom of the editor.

In TinyMCE 6.5.1, updates were made to the bounds calculation so the dismissal of the toolbar only occurs after the user scrolls past the bottom of the editor.

Previously, when the user modified a field within the Table Properties dialog, upon saving, the modified change set in the Cell Properties dialog would be replaced by the corresponding properties from the Table Properties dialog, even if the latter properties were not actually changed.

For example, if the user

the modified border width and color of the cell reverted to the corresponding values from the Table Properties dialog upon saving.

This undid the initial modifications in the Cell Properties dialog.

In TinyMCE 6.5.1, the Table Properties dialog will continue to be the source of truth and have the ability to overwrite cell and row properties like border width and color. However, the Table Properties dialog will only overwrite those properties if they were modified in the Table Properties dialog.

Previously, if there was a non-editable element in the text-selection, inserting or applying a bullet or numbered list to the selection failed. As a consequence, when the user pressed the insert list button while a non-editable element was included in the selection, nothing happened.

For TinyMCE 6.5.1 the logic for inserting lists was updated. With this update everything within the selection — except for the block element with a contenteditable="false" attribute set — is turned into a list.

In previous versions of TinyMCE, pasting content into the editor would not fire an input event.

This is contrary to web standards, which states that an input event should be fired when the value of a <textarea> element is changed.

In TinyMCE 6.5.1, a beforeinput event and an input event, both with an insertFromPaste inputType property, are now fired in order when content is pasted into TinyMCE.

In addition, the beforeinput event will also hold a DataTransfer object which contains the text/html data being pasted.

In previous versions of TinyMCE, context menus and menu items could overflow beyond the editor’s bounds when the parent node was a Shadow root.

Prior to this update, TinyMCE only supported the Shadow DOM API if its container node was a child of the Shadow root.

To address this overflowing menu issue, TinyMCE 6.5.1 added support for the Shadow Dom API when the editor’s container node is a parent of the Shadow host node.

Context menus and menu items are now constrained within the scrollable container if the editor’s root node is a parent of the Shadow host node.

In TinyMCE 6.5.1, instructions for using the editor resize handle were introduced, however these instructions are only provided in English.

Translations for these instructions will be added in a future enterprise release.