Skip to content

Block Supports: Bail early in state styles when a block has no style attribute - #13051

Draft
mukeshpanchal27 wants to merge 1 commit into
WordPress:trunkfrom
mukeshpanchal27:perf/block-states-early-return
Draft

Block Supports: Bail early in state styles when a block has no style attribute#13051
mukeshpanchal27 wants to merge 1 commit into
WordPress:trunkfrom
mukeshpanchal27:perf/block-states-early-return

Conversation

@mukeshpanchal27

Copy link
Copy Markdown
Member

Trac ticket:

Use of AI Tools


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.

…attribute.

`wp_render_block_states_support()` is registered on `render_block`, so it runs
once per block on every request. Before determining that a block has no state
styles, it performed a block type registry lookup, resolved global settings via
`wp_get_global_settings()`, and computed responsive media queries through
`WP_Theme_JSON::get_viewport_media_queries()`.

Every CSS rule the function can produce is keyed off the block's `style`
attribute, and the function already returns the content unchanged when no rules
are generated. Bailing out as soon as `style` is absent is therefore
behaviour-preserving, and skips that work for the overwhelming majority of
blocks, which carry no `style` attribute at all.

Measured on trunk with a `core/paragraph` block that has no `style` attribute:
1396.6 ns/block before, 100.4 ns/block after. Output verified byte-identical
across styled and unstyled fixtures for `core/button`, `core/navigation-link`,
and `core/paragraph`, plus empty-style, no-attrs, and unregistered-block cases.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@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.

@mukeshpanchal27 mukeshpanchal27 self-assigned this Aug 14, 2026
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