The command search field at top of post editor does not anymore self-adjust to width of browser window

[joergwiesner]

The command search field (inside text: "CTRL + K" ) on top line in post editor since WP 6.7, also in 6.7.1, does not anymore self-adjust to the width of the browser window. In consequence when narrpwing the browser window it soon overlaps the "Save" button on its right, thus makingthe "Save" button unaccessible.

[yogeshbhutkar]

Hi @joergwiesner,

Thank you for raising the ticket.

I attempted to reproduce the behavior and observed that the command search field's width is responsive, adjusting appropriately based on the browser's viewport. Additionally, I did not encounter any overlapping issues with the save button during testing.

Here are the details of my testing environment:

WordPress Version: 6.7.1
Tested on WordPress Trunk branch: Version 6.8-alpha-59274-src

Could you confirm if the behavior persists when external themes and plugins are disabled? This would help isolate the issue further.

[abcd95]

Hey @joergwiesner, Thanks for bringing this up.

The layout issue you're experiencing appears to be related to the interaction between custom plugin icons and the command search field.

I was able to reproduce this after installing multiple plugins that created custom icons in my post editor and the "Save" button was misplaced on the small screen.

Plugins Installed - Elementor 3.25.4, Yoast SEO
Testing with screen width - 477px

Screenshot - ​https://postimg.cc/62tKhj5Y

However, It is to be noted that this layout issue only occurs when there are multiple plugin icons interfering.

[sabernhardt]

This is the same basic issue as ​https://github.com/WordPress/gutenberg/issues/67069

It already has a merged change. If you could test whether that meets your needs, possibly using next week's plugin version 19.9, that would help.

I'll close this ticket, but please feel free to continue the discussion on the Gutenberg issue.

[johnkelvin1]

Replying to sabernhardt:

This is the same basic issue as Github issue No.6709

It already has a merged change. If you could test whether that meets your needs, possibly using version 19.9 of the Gutenberg plugin when that is available, that would help.

I'll close this ticket, but please feel free to continue the discussion on the Gutenberg issue.

Thank you so much for the update! That’s great to hear a fix has already been merged. Really appreciate all the work that’s gone into this. I’ll follow the GitHub issue for any further updates.