Make WordPress Core

Opened 5 weeks ago

Closed 5 weeks ago

#63298 closed feature request (worksforme)

6.8 splits post editing into 2 windows

Reported by: lilgames's profile LilGames Owned by:
Milestone: Priority: normal
Severity: major Version:
Component: Editor Keywords: changes-requested
Focuses: ui Cc:

Description

Although you'll say this is a feature not a bug, this change has a negative impact and there is no setting or preference to toggle it:

When editing/adding a new post, any custom fields, or extra stuff added by a plugin (such as SEO fields etc) are now all crammed into a very short bottom window with its own scroll box.

Editing these requires manually dragging the window resizing widget up, then scrolling inside that window to edit. Then if we want to go back to editing the main post content, we have to shrink the window back down to see the post content. This is highly annoying and slows down the editing workflow compared to previously when we could just scroll the entire window up and down. (Some of us use a mousewheel to do this really quickly! Moving a mouse pointer, clicking, dragging, and then scrolling is WAY more steps than the old way)

Either revert this change or provide us a preference to toggle it back to the previous single window layout.

Attachments (1)

wordpress-6.8-editor-usability-issue.png (108.9 KB) - added by LilGames 5 weeks ago.

Download all attachments as: .zip

Change History (2)

#1 @jorbin
5 weeks ago

  • Focuses accessibility removed
  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed
  • Version 6.8 deleted

Hi @LilGames, welcome to WordPress Trac.

This change was an intentional change that started rolling out in WordPress 6.7, see https://github.com/WordPress/gutenberg/pull/64351 https://github.com/WordPress/gutenberg/pull/64247 and https://make.wordpress.org/core/2024/10/18/post-editor-iframing-with-meta-boxes-in-wordpress-6-7/

If you would like to provide feedback, you are welcome to comment on closed issues (such as the first one linked above which is where the code change initiated), it's not necessary to create a new ticket.

Closing as worksforme since this change was intentional.

Note: See TracTickets for help on using tickets.