Changes between Initial Version and Version 1 of Ticket #65328
- Timestamp:
- 05/22/2026 09:27:17 PM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #65328 – Description
initial v1 2 2 3 3 4 In WordPress 7.0, the Distraction Free Writing (DFW) button no longer appears in the TinyMCE toolbar, indicating the feature was removed or disabled. However, wp-admin/js/editor-expand.js still contains code that registers the DFW button with TinyMCE and immediately hides it during the editor initevent:4 In WordPress 7.0, the Distraction Free Writing (DFW) button no longer appears in the TinyMCE toolbar, indicating the feature was removed or disabled. However,`wp-admin/js/editor-expand.js` still contains code that registers the DFW button with TinyMCE and immediately hides it during the editor `init` event: 5 5 6 {{{ 6 7 editor.on( 'init', function() { 7 8 if ( button.disabled() ) { … … 9 10 } 10 11 } ); 12 }}} 11 13 12 This button.hide() call triggers a TinyMCE reflow/repaint cycle (via theme.js) at a moment when the new React-based admin UI introduced in 7.0 has not finished laying out. The result is an incorrect height being stamped onto #mceu_31-body, causing the TinyMCE editor area to render with a large empty gray space. 13 The bug is intermittent because it is a race condition between React finishing its layout and TinyMCE firing init. It reproduces most reliably on a hard refresh (Shift+F5). 14 This `button.hide()` call triggers a TinyMCE reflow/repaint cycle (via `theme.js`) at a moment when the new React-based admin UI introduced in 7.0 has not finished laying out. The result is an incorrect height being stamped onto `#mceu_31-body`, causing the TinyMCE editor area to render with a large empty gray space. 15 The bug is intermittent because it is a race condition between React finishing its layout and TinyMCE firing `init`. It reproduces most reliably on a hard refresh (`Shift+F5`). 16 14 17 Steps to reproduce: 15 18 16 Install WordPress 7.017 Use the Classic Editor (either via the Classic Editor plugin or add_filter( 'use_block_editor_for_post', '__return_false' ))18 Open any post for editing19 Hard refresh (Shift+F5) repeatedly until the bug appears19 - Install WordPress 7.0 20 - Use the Classic Editor (either via the Classic Editor plugin or `add_filter( 'use_block_editor_for_post', '__return_false' )`) 21 - Open any post for editing 22 - Hard refresh (`Shift+F5`) repeatedly until the bug appears 20 23 21 24 Expected result: TinyMCE editor renders at the correct height. 22 Actual result: #mceu_31-body receives an inflated inline height (e.g. 459.391px) while the inner #content_ifr iframeis a normal size, leaving a large gray gap.23 Root cause: The DFW button registration and hide logic in editor-expand.jswas not removed when DFW support was dropped in 7.0. Removing that block should resolve the issue.25 Actual result: `#mceu_31-body` receives an inflated inline height (e.g. 459.391px) while the inner `#content_ifr iframe` is a normal size, leaving a large gray gap. 26 Root cause: The DFW button registration and hide logic in `editor-expand.js` was not removed when DFW support was dropped in 7.0. Removing that block should resolve the issue. 24 27 Workaround: None confirmed beyond avoiding hard refreshes.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)