Hide HTML tab by default

[scribu]

Most users shouldn't be editing raw HTML.

Take regular word processors. Does Microsoft Word or even OpenOffice have a noticeable button that allows you to edit the underlying XML of a document? That would be a nightmare.

So why should an average user see the HTML tab, by default?

The setting in the profile should allow one or the other, or both modes:

Editing modes:

[x] Visual editor
[ ] Raw HTML

[GamerZ]

I disagree with this. How I wish sometimes I can edit the underlying code of MS Words because formatting it is a PITA.

[sivel]

-1 from me too. Matt Mullenweg has said in the past that depending on the type of content he is writing he will use one or the other. I do the same thing and am sure there are others who do this as well.

[westi]

-1 - This is by design and we have got to this better place by a long and wandering route.

Sometimes you do need HTML mode and sometimes not.

Closing as WONTFIX.

## Summary

Follow-up to #11108. Makes the command palette trigger a native admin bar group element instead of a regular node in root-default, as ​suggested in review.

• Registers command-palette as its own group under root using add_group(), with the trigger node inside it — this produces a sibling <ul> to root-default and top-secondary
• Converts .quicklinks to display: flex so the three groups lay out naturally: left items, centered command palette, right items
• Both side groups use flex: 1 1 0; min-width: fit-content — equal space when the viewport is wide (perfect centering), but they won't shrink below their content on narrow viewports
• Command palette group uses flex: 0 0 auto between them

Existing float declarations on <li> elements become harmless (floats are ignored on flex items per CSS spec).

## Test plan

• [ ] Load any wp-admin page: command palette button should appear centered in the admin bar
• [ ] Click it: should open the command palette
• [ ] Check front-end pages: button should NOT appear
• [ ] Resize viewport — left group should push the command palette rightward rather than shrinking
• [ ] Test RTL layout
• [ ] Test mobile viewport (admin bar collapse behavior)
• [ ] Test different color schemes (modern, default)

🤖 Generated with ​Claude Code

So the command palette is not accessible on mobile. Why shouldn't it be?

It's the same as #11108, I don't think I changed anything there. I guess it will have to be added explicitly to the mobile version of the admin bar

With several plugins installed, the search bar may become misaligned:

I think that's fine, it still looks ok?

When I open the editor, you may find the search bar overlapping, which can be a bit confusing:

What o you mean here? What overlaps what?

Personally, I think going with ​https://github.com/WordPress/wordpress-develop/pull/11160 might have the least impact. What do you think? cc @sabernhardt

Would need approval from design

Something that looks like an input/search field but isn't one feels wrong.

When I open the editor, you may find the search bar overlapping, which can be a bit confusing:

What o you mean here? What overlaps what?

They're not overlapping, but there are two of these bars right next to each other.

What overlaps what?

I was referring to these two places. There are two search bars close to each other that both trigger the command palette.

@t-hamano Isn't that a problem in your PR too? How has it been addressed elsewhere? Or is there a proposal to unify them.

Something that looks like an input/search field but isn't one feels wrong.

@ocean90 It's the same for the editor document bar 🙂

Isn't that a problem in your PR too? How has it been addressed elsewhere?

Two approaches have been proposed that do not use a search bar in the first place.

• ​https://github.com/WordPress/wordpress-develop/pull/11160
• ​https://github.com/WordPress/wordpress-develop/pull/11063

Personally, I think going with ​https://github.com/WordPress/wordpress-develop/pull/11160 might have the least impact. What do you think?

Chatting with @mtias about this and a more condensed command‑K control is okay for beta 3 if needed, rather than the search icon. The search icon alone is not enough.

Let's land this ahead of the next beta so we can get more testing. Previously, the smaller command‑K control would have worked to get an initial version in to a prior beta but, at this point, it's important we stick with the design and project leadership direction.

This looks good. Please land this so we have time to test sooner rather than later.