Allow Disabling of Editor Command Palette

[MadtownLems]

What problem does this address?

6.6-beta-1 looks to include the Command Palette in the Post Editor. This addition looks to be very confusing for our users, and provides very little - if any - benefit. We'd really like to not have to educate our large number of content providers on it, especially if the education ends up being: "Just ignore it"

What is your proposed solution?

Add a filter, ideally through block_editor_settings_all (https://developer.wordpress.org/reference/hooks/block_editor_settings_all/) that lets users easily disable the Editor Command Palette.

[annezazu]

Just a quick note that the command palette has been available in the post editor for quite some time (since 6.3). It's not new to 6.6.

[MadtownLems]

Just a quick note that the command palette has been available in the post editor for quite some time

Correct - but 6.6 makes it prominently displayed at the top of the post editor. This will definitely be the first time that any of our content providers are aware of it, and shown to hit Ctrl+K to open it

[annezazu]

Yes! That's part of the work done here with 6.6: #52632 It's important to note though what's new for each release when deciding what can be fixed or changed in this beta period hence the note from yours truly :)

[ndiego]

Add a filter, ideally through block_editor_settings_all (https://developer.wordpress.org/reference/hooks/block_editor_settings_all/) that lets users easily disable the Editor Command Palette.

I agree. There should be Editor setting that controls whether the Command Palette is available or not. This setting should default to true, but allow developers to disable it in specific Editor contexts.

[MadtownLems]

To complicate this issue, I learned that the only way to go "Back" from "Edit Original" pattern exists in the Command Palette. If disabling the Command Palette is supported, there should be an alternative method to go 'back' to the page/post you were working on in that context.