This document is only provided as a preview. It is under development and is subject to substantial changes. Consider the included information incomplete and use it with caution. The Release Notes provide high-level coverage of the improvements and additions that have been implemented in TinyMCE 5.0 Beta and document known problems in this release, as well as notable bug fixes, Technology Previews, deprecated functionality, and other details.
TinyMCE 5.0 has an ARIA WCAG 2.1 standards compliant user interface to make the user interface controls and dynamic content more accessible. In TinyMCE 5.0, more complex controls or dialogs can be written in the new API style while keeping the more straightforward methods of adding buttons and windows the same.
Include this line of code in the <head> of the HTML page and link to the tinymce.min.js source file:
Signing up for a free API key provides entitlements to premium Image Tools plugin. A cloud image proxy server must already be configured. Premium plugins can be purchased at any time once the API key has been set up.
Refer to the Quick start docs for more information.
Developers can upgrade their TinyMCE 4.x instances to TinyMCE 5.0 with little or no fuss. For instructions on how to migrate, refer to the Migration Guide.
Note: An instance of TinyMCE with heavy customizations could take longer to upgrade. Please contact Customer Support if encountering issues with the upgrade.
Try out TinyMCE 5.0 demo to explore the new UI.
The following new features were added to the TinyMCE 5.0 Beta version.
The context menu is a new configurable component added in TinyMCE 5.0 . It appears when the user right-clicks in the editable area. By default, it does not disable the operating system’s native context menu, if there are no items to display at the cursor position the native context menu will be shown. The context menu supports both individual menu items and dynamic context menu sections. Refer to the context menu documentation, for more information.
A context toolbar is a pop-up toolbar that appears when a specific type of content is focused. It contains the toolbar buttons relevant to that content. The context toolbar makes a limited number of relevant choices more visible and readily accessible. Refer to the Context Toolbar documentation, for more information.
The Custom Menu items configurations options has changed in TinyMCE 5.0. The
addMenuItem has a new configuration. A new method
addToggleMenuItem has been added which is an explicit method for creating toggle menu items similar to the new special toolbar button methods. Refer to the configuration documentation, for more information on
The Dialog component is created for showing dialogs (sometimes referred to as modals) in the user application. The plugin supports the use of dynamic content for all aspects and is easily configurable and overridable. To display simple information, e.g., a source code plugin displays the HTML code from the content in the dialog.
TinyMCE is up-to-date with the latest accessibility standards. This includes the review of shortcuts and ensuring tooltips when used with keyboard navigation. The editor can now reflect accurately where and what a user is interacting with. A new experimental feature has been added that allows using the tab across all TinyMCE toolbars, sidebars, content, and footer bar. This allows more granular control to quickly jump to the appropriate editor control and then navigate down to its specific feature sets.
TinyMCE is the only editor to have this feature!
TinyMCE 5.0 codebase has been extensively rewritten with the focus on converting the UI components to a more modern UI framework. As a consequence of this rewrite, all the related features have been updated. The new framework takes advantage of the latest CSS3 features for consistent styling and is ARIA IBM standards compliant. The new UI framework has a stricter API for creating components, which means that the code is more structured and has an in-built validation combined with TypeScript. This strictness makes the code cleaner, more stable, and easier to maintain and troubleshoot.
TinyMCE 5.0 uses a new theme Silver and a new skin Oxide which uses more modern CSS such as
A Skin in Tinymce is used to make changes to the appearance of the editor, for example, colors, margins, paddings, fonts, icons, etc. A Theme creates the editor construction (left, top, bottom, or right of the editing area - vertical or horizontal, inline or outside, etc.). A skin usually changes the color scheme of a button, dialog, etc. while the theme applies to the whole editor including its functionality and has child skins to change the appearance.
In TinyMCE 5.0 the Silver theme contains a set of configurable UI components that could be used to replace the current customizations (modern, inline, and inlite theme). Silver is enabled by default if a theme is not specified.
The skin creator is coupled with the
tinymce.ui framework, so it works with the modern theme, the inlite theme, and to some extent MoxieManager.
Tables are better in TinyMCE 5.0 editor. Creating and configuring tables in TinyMCE 5.0 is less cumbersome. We have enhanced this feature by modifying the code to ensure the styles are correct and consistent. The Styles text field has been removed from the advanced table of the dialogs. The code is now much less confronting and confusing for non-developers. This also means more control can be exercised over the table styles to ensure better the styles are correct. The process of how styles are set and retrieved from tables, rows, or cells, have been improved to d be more reliable. “Border” input field in the table properties dialog is now called “Border width” for clarity. Refer the Tables documentation, for more information.
Using CSS for styling - TinyMCE 5.0 uses CSS more for styling. Thus few legacy and outdated data attributes that were being configured on tables, rows, and cells and no longer adhered to the industry best practices, were removed. HTML is now cleaner and shorter.
Autofill Values - In TinyMCE 5.0, the Autofill feature is used while opening a properties dialog with a single table, row, or cell selected. The dialog will fill automatically with the relevant existing values. In TinyMCE 4.x., if multiple rows or cells are selected to open the relevant properties dialog, all the dialog fields are left blank. In TinyMCE 5.0, fields which have the same values for all the selected rows or cells are filled automatically, and the fields which have no existing value or have different values are left empty.
TinyMCE 5.0 uses SVG icons for a better crisp look. Buttons are now added via methods in
editor.ui.registry rather than
editor.ui.registry.addButton() instead of
editor.addButton(). To make the creation of custom toolbar buttons easier, new methods were added for split, toggle, and menu toolbar buttons with configuration options specific to the button type. Refer the Toolbar Buttons documentation, for more information.
The new TinyMCE 5.0 has a better UI accessibility for a diverse set of users. Tiny is committed to adhering to WCAG 2.1 standards to ensure content is accessible to everyone. TinyMCE UI can be mouse or keyboard driven. The new UI delivers a consistent user experience when used with screen readers or browsers in various modes like high contrast on both mobile and desktop platforms. TinyMCE 5.0 conforms to WCAG 2.1 standards and has a stricter editor UI and workflow to offer a much more accessibility-compliant interface and a consistent workflow. While this may impact a developer’s customization abilities, they receive a more overall consistent user experience.
Technology previews provide a way to access the upcoming technological innovations. The technology preview is created as a courtesy to the community of developers and the community of users to get feedback and make this technology better. In the process of making these previews generally available, Tiny endeavors to resolve all the issues reported by customers or internal and external developers.
It is important to note that these “Tech Previews” are not fully supported under the Tiny Cloud service level agreements. These previews are not recommended for deployment in production and are for testing purposes only.
Please provide feedback or contact us for support.
In TinyMCE 5.0, some configurations have been removed because they are no longer necessary or an improved solution has been introduced. Refer to the Migration Guide, for more information.
| ||Owing to the enhancements to the new inline toolbar behaviour, |
| ||Owing to the changes in the menus and removal of the |
|BeforeRenderUi||Fired before the UI was rendered.|
Listbox is no longer a supported toolbar button type in TinyMCE 5.0. Though listbox has been removed, any functionality provided by custom listbox toolbar buttons can be retained by switching to a different kind of toolbar button using the new methods. The recommended toolbar button type to switch to is the Split button.
The following plugins from TinyMCE 4.x do not require height or width options to be specified in TinyMCE 5.0:
Refer to the Migration Guide, for more information.
Some UI configurations in TinyMCE 5.0 have changed due to an updated UI engine. Please see this section of the Migration Guide for more information.
This section describes issues that users of TinyMCE 5.0 may encounter, as well as possible workarounds for these issues.
In TinyMCE Developers Preview version, pages were slow to respond on Chrome. The responsive issue was caused by excessive use of memory when multiple inline editors were used. This issue was fixed by optimizing the way the inline editor consumes memory. The inline editor’s deactivated state was improved to consume less memory when it was not being used. When the inactive editor becomes active again, its full capabilities are restored. This optimization resulted in only one active editor consuming memory while the others are in a dormant, ready state.
Previously, it was possible to create new UI controls by extending existing controls. In the current version of TinyMCE, the UI controls are not exposed in the API directly. Hence, it is not possible to create new UI controls by extending existing controls. This functionality was changed to provide flexible components that did not need to be extended, making it easier to create dialogs that adjust to the active skin. The reduced API surface is also easier to maintain. Based on more customer feedback and use cases, this functionality may be extended to provide more flexibility to create new UI controls.
In TinyMCE Developers Preview version, when the focus was on the source input, the tab did not shift the focus to the source button. This issue was being caused due to the size input lock component not reading dimensions -> width, or dimensions -> height. As a consequence of this issue, image list select box up and down arrow did not change the content. To resolve this issue, the code was restructured to read the the label context. This issue also affected the dialog select component task. This issue has been fixed in the current release of TinyMCE.
Previously, when the context menu for a link was opened by pressing the
Shift+F10 keys or right-clicking on the link, pressing
Esc key closed the context menu. In the current version of TinyMCE, this feature does not work as expected. This issue will be fixed in the future release of TinyMCE.
Previously, when the focus was on a split button, there were no focus outlines and pressing the
Enter key created a list item. In the current version of TinyMCE, the split section appears when the
Shift+Enter keys are pressed without any notifications to the user. The colorpicker and datetime plugins also have the same issue. To fix this issue in the future release of TinyMCE, the operation of opening the menu by pressing the
Shift+Enter keys will have user notifications.
In the current version of TinyMCE, There is no way to know if a button is pressed or not. This behavior is expected for the language options when the
Shift+Enter keys are pressed. This issue will be fixed in the future release of TinyMCE.
Previously, when the focus was on the spellcheck button, pressing the right arrow key shifted the focus to the next button. In the current version of TinyMCE, this does not work as expected. This issue will be fixed in the future release of TinyMCE.
The following issues were reported in the current TinyMCE UI:
- In the current version, when English is selected from the language options, there is no tick mark in the UI. This operation is notified through verbal announcement only.
- In the current version, autocorrect does not announce when a word changes.
- In the current version, spelling highlights do not have an attribute
aria-invalid="spelling"for assistive tools to announce when the cursor has entered a misspelled word.
The above issues will be fixed in the future release of TinyMCE.
The community was invited to test the TinyMCE 5.0 editor and report bugs and issues in the Developers Preview release. The following issues have been fixed in the TinyMCE 5.0 Beta version.
The new TinyMCE 5.0 editor comes with significant changes to the previous versions. Tiny has created a more configurable and modern editor. Improved solutions have been introduced for unnecessary and obsolete configuration options. Please see the Editor-Core section in the Migration Guide for more information.
|AP-36||Add Types to Alloy|
|AP-38||Scope Alloy Project|
|AP-46||Integrate alloys pub sub messaging with tinymce|
|AP-47||[dialog H] create a help menu in Alloy|
|AP-49||cleanup alloy types|
|AP-51||SPIKE: Investigate typed Alloy on the Mobile theme|
|AP-57||Add Types to Boulder|
|AP-71||Fully type alloy|
|AP-144||Port status bar to alloy|
|AP-409||Add types to lumber|
|AP-407||Add types to Sand|
|AP-415||Add types to Jax|
The following browser related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-158||First automated test run: Make all browsers pass all relevant tests|
|AP-182||Cross Browser Tests : Setup & run tests against the OS/Browser combinations|
|AP-240||Safari: Unable to select all using keys when there are anchors in the text editor|
|AP-248||Firefox: Cannot use |
|AP-269||Incorrect display of IFrame border (Chrome/Safari)|
|AP-357||IE11 Issue with SVG icons|
The following Colorpicker related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Colorpicker docs for more information.
|AP-87||Create colorinput component|
|AP-207||Color Picker - Not applying color selection|
|AP-210||Color Picker - button should not be visible if color picker is not in the list of plugins configured|
|AP-216||Change color picker dialog title to “Color” to match Tiny 4.8.2|
|AP-239||Keyboard navigation within the Colorpicker|
|AP-317||Colorpicker’s inputs are not being given the right class.|
|AP-372||If “color_picker_callback” in place then on selecting colorpicker no colorpicker should popup and the color in callback should be applied|
|AP-142||Font color and Background color palettes|
|AP-284||Unable to apply forecolor and backcolor to the text in the table|
|AP-286||ColorInput gives an error saying the panel is an unknown component.|
The following editor related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-22||[T5] create type interfaces for tinymce components|
|AP-52||SVG implementation details|
|AP-72||Fix type error in Transformer|
|AP-73||Change bridge version to latest|
|AP-84||Fix type errors on develop|
|AP-92||Add types to Agar|
|AP-94||Add configuration for typeahead responseTime|
|AP-95||Add shiftKey support to bedrock keyeffects|
|AP-104||Add some useful chain assertions to Agar|
|AP-105||Chain.isInput fails on undefined|
|AP-106||Add formChange event to Input fields|
|AP-108||API for switching tabs|
|AP-117||Change Typeahead to pass though change events|
|AP-126||Display placeholder when typeahead menu is empty|
|AP-127||remove PatchEditor and use bridge|
|AP-147||Standardise test code format|
|AP-151||Update TransformFind types to return Option instead of Option |
|AP-172||Get menus working from init config|
|AP-176||Add logging methods for standardised QA to Agar|
|AP-178||Think of ways to simplify the onSetup API for customers.|
|AP-180||selection.selectorChanged needs a way to unbind handlers|
|AP-188||Find and Replace -functional issue|
|AP-190||Pressing left and right with an open menu should navigate to the next menu|
|AP-195||Editor crashes when pagebreak_separator set to empty string|
|AP-199||Expanded SlotContainer behavior API|
|AP-200||Fixed Sliding behaviour responding to nested transitioned events and incorrect type definition for grow|
|AP-206||Menu items - Enabled when focusing out of menu item|
|AP-211||On focus styles|
|AP-219||remove extra div wrapping from .tox-tinymce|
|AP-256||Cleanup Editor for public Preview|
|AP-262||size lock ratio|
|AP-267||Tall menus cause scroll jump with a small window|
|AP-273||Bottom positioned menus appear in the wrong spot initially|
|AP-283||Re-enable all tinymce tests|
|AP-312||Cap the width of menu items with ellipsis.|
|AP-359||Font size select issues|
|AP-373||General - editor does not autoscroll when pressing enter.|
|AP-379||An empty editor causes issues with the statusbar because of iframe wrap min-height|
|AP-381||Broken keyboard shortcuts - Windows|
|AP-430||Page responsiveness with multiple inline editors|
|AP-445||Keyboard shortcut anomalies|
|AP-452||Update Chain/Step |
TinyMCE 5.0 has an ARIA WCAG 2.1 standards compliant user interface to make the user interface controls and dynamic content more accessible. The user interface logic has been changed entirely in TinyMCE 5.0. Refer to the Migration Guide, for more information on the UI changes.
|AP-314||Fix memory leaks in theme. There are a few events which need to be unbound.|
|AP-334||Select boxes are broken|
|AP-344||importcss_append configuration is not working as expected|
The following CSS related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-143||Styles select dropdown & ImportCss|
|AP-183||create a Css solution for dialog width/height|
|AP-201||Refactor the menu CSS to be more generic|
|AP-203||Need to make a content.inline.min.css|
|AP-393||style_formats API is not fully supported|
|AP-453||TinyMCE 5 DP doesn’t support css values in height option|
The following Skin related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-30||Make oxide an npm module on nexus|
|AP-31||wrap Oxide project in npm and build script to export css|
|AP-77||Compile Oxide Styles in tinymce|
|AP-78||Add oxide classes to Preview dialog|
|AP-131||create packaging for the Apollo skin|
|AP-187||Cleanup css styles from demos, move to oxide|
|AP-384||Dialog headings (the titles) are styled wrong. Apply correct classes or update|
The following theme related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-79||Improve types for SilverDialog|
|AP-91||Use more Bridge types in SilverDialog|
|AP-96||Bug: Error when closing SilverDialog|
|AP-139||Adapt mcagar to silver|
|AP-194||Support inline mode on the silver theme|
|AP-308||Update Mobile theme to work (maybe: pull into silver)|
The following Context Form related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Context Form docs for more information.
|AP-274||Separate ContextForm API into launch and form (and||DOCument how it works)|
|AP-301||Navigating through a link flickers and moves the context form|
The following Context Menu related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Context Menu docs for more information.
|AP-11||image tools context menus|
|AP-12||Spell Checker Context menu|
|AP-16||Table context menus|
|AP-109||Spike a new context menu for apollo that works similar to tbio|
The following Context Toolbar related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Context Toolbar docs for more information.
|AP-148||Create a context toolbar|
|AP-243||Context toolbar overflows outside the container when page is scrolled|
|AP-268||Context toolbar contained in a scroll box|
|AP-297||Use Ctrl+F9 to focus the context toolbar. Escape should focus the editor again.|
|AP-318||Improve contexttoolbar positioning near edge of editor|
|AP-327||Update context toolbar position on editor resize|
The following Dialog related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Dialog docs for more information.
|AP-17||[dialog L] Insert Anchor|
|AP-18||[dialog L] Source Code|
|AP-19||[dialog L] codesample|
|AP-20||[dialog L] color picker|
|AP-21||[dialog H] Image dialog|
|AP-43||[dialog L] Preview|
|AP-45||[dialog] Find and Replace dialog|
|AP-48||[dialog] create special chars dialog|
|AP-50||[dialog L] docment Properties (Fullpage)|
|AP-55||[dialog M] Insert Link|
|AP-61||Create styles for a pick swatch dialog|
|AP-70||Spike a dialog API for discussion|
|AP-74||Fix classes used on TextField and make label optional|
|AP-81||Wire dialog values through TabPanel|
|AP-82||Implement Grid component|
|AP-83||Create a Dropzone component|
|AP-88||Fix type and lint errors|
|AP-89||Pass through extra information to typeaheads|
|AP-90||Add change behavior to SelectBox|
|AP-93||Search replace dialog tabbing from replace to check box does not work|
|AP-97||Make a confirm dialog|
|AP-98||[dialog L] Code dialog|
|AP-100||[dialog H] image tools|
|AP-101||[dialog L] Table properties dialog|
|AP-102||[dialog L] Template dialog|
|AP-103||Implement Size component|
|AP-114||Design approach for handling multiple-screen dialogs|
|AP-122||Make Dialog Buttons Great Again|
|AP-124||Integrate dialog busy feature|
|AP-137||Dialogue - Find and replace - Except “Find” all other buttons should be disabled by default|
|AP-184||Create UI for image tools dialog|
|AP-208||Add preview label to the text field in the Template dialog|
|AP-209||Help dialog has ‘Ok’ and ‘Cancel’ buttons instead of ‘Close’|
|AP-212||Table dialog: Colorpicker tab doesn’t close on clicking Ok|
|AP-214||Keyboard navigation in advanced tab of table dialog|
|AP-217||Preview dialog doesn’t close on escape|
|AP-218||[Notifications] Template dialog throws error when trying to open it without configured templates|
|AP-220||SearchReplace dialog: Prev button doesn’t become enabled|
|AP-221||Table Dialog: Color picker transfers focus from dialog to body on clicking Ok|
|AP-222||SearchReplace & Anchor: Alert dialog has ‘Close’ button instead of ‘Ok’|
|AP-223||SearchReplace & Anchor & Table: Alert dialog has the ‘Ok’ button on the left side of the window|
|AP-241||Can’t refocus dialogs by clicking on dialog body|
|AP-252||Dialogs size and responsiveness|
|AP-253||Show dialogs with backdrop|
|AP-260||The typeaheads in dialogs need styling on the containers that their menus show up in, so that they can be seen above the dialog|
|AP-265||Source code dialogue anomalies|
|AP-272||Incorrect dialogue focus|
|AP-276||Can’t align row using row properties dialogue|
|AP-291||Dialog checkboxes have no focus indication|
|AP-293||Link dialogue anomalies|
|AP-315||dialog checkbox does not refire a dialog onChange event|
|AP-329||tabbed dialogs shrinking when no results returned|
The following Menu related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version.
|AP-2||Clarify Icon declaration for buttons and menuItems|
|AP-76||Reimplement Buttons and MenuItems using Bridge register|
|AP-280||Menu check marks should be on the left|
The following Toolbar Buttons related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Toolbar Buttons docs for more information.
|AP-1||Clarify inner button creation for Public API|
|AP-28||Make menu item buttons for the file toolbar|
|AP-33||Make Toolbar and button Groups for Toolbar|
|AP-54||Make general toolbar button|
|AP-64||[T5] plugins A-C update to the new addButton, Addmenu APi|
|AP-65||[T5] plugins D-L update to the new addButton, Addmenu APi|
|AP-66||[T5] plugins M-S update to the new addButton, Addmenu APi|
|AP-67||[T5] plugins T-W update to the new addButton, Addmenu APi|
|AP-68||[T5] plugins all Premium plugins - update to the new addButton, Addmenu APi|
|AP-136||tab navigating radio buttons is broken after clicking a radio button|
|AP-152||Generalise toolbars in preparation for context toolbars.|
|AP-155||Identify the bridge requirements for existing / proposed toolbar / menubar.|
|AP-175||Create a sidebar component|
|AP-186||Core “plugins” - update to the new addButton, Addmenu APi|
|AP-189||Editor configuration “height” not functional with full set of toolbar items & toolbar items should break and rollover as per the height settings|
|AP-226||Update complex format controls to new button api, etc.|
|AP-250||Disabled toolbar button styles.|
|AP-251||Ensure keyboard navigation works with disabled toolbar buttons.|
|AP-259||Slow tool tips, when hovering over a toolbar button|
|AP-258||Undo and redo buttons should be disabled unless there is an undo or redo state|
|AP-264||Alignment toolbar buttons can get out of state|
|AP-275||Empty toolbar items give ‘No representation for toolbarItem: ‘ errors.|
|AP-290||Defaulting toolbar is missing|
|AP-295||SplitButtons (and normal Buttons) toggle as you click them (rather than just relying on the state)|
|AP-310||Menubuttons (and dropdowns in general) are not using the icon packs|
|AP-303||Status bar word count needs correction|
|AP-307||Menus should open as you hover over them, once you have a menu open.|
|AP-321||Block formatting toolbar should have a default ‘Formatting’ title when there is no selection|
|AP-371||Stop icon is displayed along with tooltip for undo and redo buttons|
|AP-377||toolbar - restore last draft icon has text displayed ( not tooltip)|
|AP-450||Filter out empty toolbar groups|
The following URL related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the URL docs for more information.
|AP-85||Make a Url input component|
|AP-118||Change Urlinput to fire formChange event|
|AP-119||Add validation icons to UrlInput|
|AP-125||Add history to UrlInput and disable anchor+headers in image mode|
|AP-128||Wire up button on URL Input|
The following issues were reported against the Comments premium plugin during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Comments docs for more information.
|AP-179||Tiny comments (premium)|
The following issues were reported against the dialogs in the premium plugin during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see our Premium Features docs for more information.
|AP-23||[dialog H] Foam plugin, accessibility (premium)|
|AP-24||[dialog M] Powerpaste 2 (premium plugin)|
|AP-25||[dialog M] Powerspell (premium plugin)|
|AP-26||[dialog L] Clerk (premium plugin)|
The following issues were reported against the Mentions premium plugin during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Mentions docs for more information.
The following Accessibility Checker related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Accessibility Checker docs for more information.
|AP-261||Accessibility checker, notification banner is broken|
|AP-330||accessibility checker not loading at all|
|AP-340||accessibility checker requires input validation|
|AP-369||AllyChecker dialogue should show “Caption cannot be empty” when left empty and click repair|
|AP-419||Accessibility checker does not work without a toolbar|
The following Advlist related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Advlist docs for more information.
|AP-288||Unable to customize advlist plugin|
The following Anchors related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Anchors docs for more information.
|AP-120||Make Typeahead dropdown anchor configurable|
|AP-174||Positioning magic for anchors|
|AP-277||Statusbar bugs (tox-edit-area height and autoresize plugin)|
|AP-424||Turn resize handler off when autoresize is enabled|
The following CharMap related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the CharMap docs for more information.
|AP-86||Create the charmap component|
|AP-115||Special chars, when mouse focus moves away from the char, focus defaults back to the first item instead of the last item that was focused|
|AP-129||Character Map mouse hover and mouse out focus states|
|AP-228||Consolidate charmap / resultsbox into Collection|
|AP-238||Charmap: Character category names need updating|
|AP-316||Character map entries do not have the active class added on mouse over|
The following Directionality related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Directionality docs for more information.
|AP-423||Directionality ltr/rtl not implemented|
The following Emoticons related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Emoticons docs for more information.
|AP-156||Create the emoticon panel|
|AP-366||emoji type ahead can mess with typing urls http:// will bring up an empty emoji typeahead result|
|AP-449||Emoji dialog intermittent failing tests|
The following Image Tools related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Image Tools docs for more information.
|AP-323||imagetools needs to handle CORS errors|
|AP-342||imagetools_toolbar configurations not functional|
|AP-346||Imagetools - Image editing area size should be consistent across all options and should not overlap on buttons below|
|AP-382||Image - context menu not appearing when image has caption|
The following Link related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Link docs for more information.
|AP-13||Link checker (premium)|
|AP-255||Link plugin, pressing insert link button without a selection causes console errors|
|AP-341||Insert link plugin: url validation component is missing|
|AP-358||Link context toolbar issues|
|AP-438||Link context form is incorrectly styled|
The following Media related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Media docs for more information.
|AP-198||Media plugin is missing media dimensions setting|
|AP-245||Media Embed premium plugin (pillow)|
The following Lists related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Lists docs for more information.
|AP-146||Create numbered list icons|
|AP-339||Num/Bullist - not reflecting the selection on toolbar|
The following Search and Replace related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Search and Replace docs for more information.
|AP-298||Find and Replace - “Match case” should not be selected by default, title and button label needs correction|
The following Table related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Table docs for more information.
|AP-197||Implement insert table MenuItem|
|AP-285||Table editing tools states can go stale after content is modified|
|AP-365||Table - resizing of split cells could be improved, sometime they are a lot larger than they need to be|
|AP-385||Caption - table properties and image|
|AP-391||Table style attribute should retain “border-collapse: collapse;” when border is set to 0|
The following Table of Contents related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Please see the Table of Contents docs for more information.
|AP-347||By default table of contents (toc) should be disabled on toolbar and should be only enabled if editor content has headings, Table of contents - contextmenu should be displayed in center not top right corner|
The following documentation related issues were reported during the developer’s preview and are now fixed in the TinyMCE 5.0 BETA version. Refer to the latest Documentation for more information.
|DOC-98||Typo - importcss_file_filter|
|DOC-103||Remove reduntant note in Tiny quick-start|
|DOC-115||Review “visual” documentation and amend the content|
|DOC-117||Remove deprecated features and content from documentation from 4.x and 5.x versions|
|DOC-118||Remove TinyMCE mobile documentation from Dev Preview|
|DOC-119||Missing documentation - Dev Preview - Editor Appearance - insert_toolbar|
|DOC-120||Correction - Skin|
|DOC-121||Correction - selection_toolbar|
|DOC-122||fontsize_formats configuration has to be changed from pt to px|
|DOC-125||Correction - Content filtering - entities|
|DOC-128||Correction - Content filtering - valid_children|
|DOC-129||Correction - Content filtering - forced_root_block|
|DOC-130||Correction - Content filtering - fix_list_elements|
|DOC-132||Correction - Accessibility keyboard shortcuts|
|DOC-133||Caption - Themes & Skin|
|DOC-135||Remove references from docs and code for “force_hex_style_colors” config|
|DOC-138||Out of sequence content|
|DOC-139||Should Anchor top/bottom documentation in link section?|
|DOC-140||Context Menu documentation page not found|
|DOC-141||Add “inlite” plugin documentation to “Add Plugins to TinyMCE” section|
|DOC-142||Amend Distraction-free documentation|
|DOC-143||Remove colorpicker and textcolor documentation|
|DOC-144||Correction - noneditable|
|DOC-145||Review and improve definition of default in advlist docs|
|DOC-148||Remove “colorpicker” and “textcolor” doc from “Add Plugins to TinyMCE” section|
|DOC-149||Remove deep nesting from docs nav menu|
|DOC-150||Correction - target_list|
|DOC-151||Update nginx redirect rules for new documentation structure|
The following Quality Assurance related issues that were carried out during the developer’s preview. We have tested and fixed these issues in the TinyMCE 5.0 BETA version.
|AP-309||Write tests for complex format controls from AP-226|
|AP-185||Create 5.0 fiddle|
|AP-445||Keyboard shortcut anomalies|
|QUAL-15||Review and contribute in technical documentation|
|QUAL-9||Verify 3.x Compatibility Plugin with Tiny 5.0|
|QUAL-6||Review exisiting Testrail Tests|
|QUAL-5||Create test summary report for Apollo (TinyMCE 5 )|
|QUAL-4||Prepare release QA Plan for Apollo (TinyMCE 5)|
|QUAL-3||Review and validate existing TinyMCE test cases on TestRail|
|QUAL-2||Sort out test environment and also document custom test environment setup steps|
|QUAL-1||Create sprint QA plan & setup a work item handover process|
Thanks for the feedback!
Can't find what you're looking for? Let us know.