Skip to content

Twenty Twenty, Twenty Twenty-One: Let full-width Details blocks fill the editor width - #14738

Open
irozum wants to merge 1 commit into
WordPress:trunkfrom
irozum:fix/59957-twentytwenty-details-block-full-width
Open

irozum wants to merge 1 commit into
WordPress:trunkfrom
irozum:fix/59957-twentytwenty-details-block-full-width

Conversation

@irozum

@irozum irozum commented Oct 22, 2026

Copy link
Copy Markdown

Summary

In the block editor, a Details block set to full width stays at the narrow content width in Twenty Twenty and Twenty Twenty-One, while the front end is already correct.

The generic .wp-block { max-width: ... } editor rule also constrains the children of the Details block. This adds .wp-block-details > .wp-block { max-width: 100%; } to the editor styles of both themes, as suggested in the ticket. Margins and front-end styles are untouched.

  • Twenty Twenty: editor-style-block.css and its RTL counterpart.
  • Twenty Twenty-One: new details/_editor.scss partial imported in blocks-editor.scss, plus the compiled style-editor.css.

Testing instructions

  1. Use Twenty Twenty or Twenty Twenty-One and add a Details block with some content in the editor.
  2. Set its alignment to Full width.
  3. Before: the block stays narrow in the editor. After: it fills the full width, matching the front end.

CSS-only change, so there is no automated test. I did not run a browser check of the editor.

Trac ticket: https://core.trac.wordpress.org/ticket/59957

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 5.5
Used for: Implementation and PR description.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props irozum.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant