Skip to content

Pattern: Disable visibility support - #81866

Open
shimotmk wants to merge 1 commit into
trunkfrom
fix/pattern/disable-visibility
Open

Pattern: Disable visibility support#81866
shimotmk wants to merge 1 commit into
trunkfrom
fix/pattern/disable-visibility

Conversation

@shimotmk

Copy link
Copy Markdown
Contributor

What?

related #76138 #76128 #78780

Why?

Pattern blocks do not have a wrapper tag. When hiding pattern blocks per viewport, the setting only applies to the first block, and the second and subsequent blocks are displayed regardless of the setting, so we disable visibility support.

How?

Testing Instructions

  1. Open a post or page.
  2. Insert a Pattern block.
  3. It is understood that visibility cannot be set.

Testing Instructions for Keyboard

Screenshots or screencast

Before After
before after

Use of AI Tools

@github-actions

github-actions Bot commented Aug 20, 2026

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. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: shimotmk <shimotomoki@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

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

@github-actions github-actions Bot added the [Package] Block library /packages/block-library label Aug 20, 2026
@shimotmk shimotmk self-assigned this Aug 20, 2026
@shimotmk shimotmk added [Block] Pattern Affects the Patterns Block [Type] Bug An existing feature does not function as intended labels Aug 20, 2026
@github-actions

Copy link
Copy Markdown

Flaky tests detected in 99e9af9.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/32356704262
📝 Reported tests:

should allow user to add and remove multiple local font files in /test/e2e/specs/admin/font-library.spec.js, passed after 2 failed attempts.
Error: expect(locator).toBeVisible() failed

Locator: getByLabel('Exo 2 Semi-bold Italic')
Expected: visible
Timeout: 5000ms
Error: element(s) not found

Call log:
  - Expect "toBeVisible" with timeout 5000ms
  - waiting for getByLabel('Exo 2 Semi-bold Italic')

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/admin/font-library.spec.js:58:6
Error: expect(locator).toBeVisible() failed

Locator: getByLabel('Exo 2 Semi-bold Italic')
Expected: visible
Timeout: 5000ms
Error: element(s) not found

Call log:
  - Expect "toBeVisible" with timeout 5000ms
  - waiting for getByLabel('Exo 2 Semi-bold Italic')

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/admin/font-library.spec.js:58:6

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

Labels

[Block] Pattern Affects the Patterns Block [Package] Block library /packages/block-library [Type] Bug An existing feature does not function as intended

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants