Opened 18 months ago
Last modified 17 months ago
#58260 assigned defect (bug)
Enable `elementpath` for the Classic Block TinyMCE editor
Reported by: | afercia | Owned by: | afercia |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Editor | Keywords: | has-screenshots has-patch |
Focuses: | Cc: |
Description
So far, the Classic Block renders the TinyMCE editor within the WordPress Editor canvas. In this case, disabling the TinyMCE elementpath
makes perfectly sense, as it would be perceived as an extraneous I element, in this context. For this reason, elementpath
is explicitly disabled in the TinyMCE settings, see https://github.com/WordPress/wordpress-develop/blob/d744c4d39729e2f1df76d93d99560d791ece3043/src/wp-includes/class-wp-editor.php#L933
See first screenshot for the current state.
However, on latest Gutenberg, the Classic Block opens a modal dialog. The TinyMCE editor renders within the modal dialog. In this context, there's no reason to disable elementpath
. The elements path shown in the TinyMCE status bar is a useful tool that helps users with selecting the elements within the editor.
Currently, the status bar shows ad the bottom of the editor, but it's empty. See second screenshot.
Attachments (5)
Change History (7)
@
18 months ago
Latest Gutenberg: rendered within a modal dialog with empty status bar and no element path.
#1
@
18 months ago
- Keywords has-patch added
- Owner set to afercia
- Status changed from new to assigned
Current state: rendered in the editor canvas with no status bar and no elements path.