Repository navigation
Fix CI e2e failures after WP 7.1 / Gutenberg 23.8 - #4274
Merged
Merged
Conversation
Gutenberg 23.8.0 (WordPress/gutenberg#81231) renders a real ghost paragraph instead of the default block appender, so a new post's canvas no longer contains `.block-editor-inserter__toggle`. The editor-frame Cypress test now asserts that the canvas stylesheets loaded by checking `overflow-wrap: break-word` on the first block, a rule from block-editor's content.css present in every supported version. The docs API reference test failed on a 404 from proxy.kapa.ai, the third-party assistant widget. The test now answers every cross-origin request with an empty response, so the widget never loads and only the docs build itself is under test.
github-actions
Bot
added
[Package][@wp-playground] Website
[Type] Documentation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Fixes CI e2e/doc test failures caused by upstream WordPress/Gutenberg UI changes and intermittent third‑party widget network errors, by making the tests assert more stable signals and isolating them from external dependencies.
Changes:
- Update Cypress e2e assertion to verify Gutenberg iframe styling via a stable, version-spanning CSS rule instead of the inserter button UI.
- Update Playwright docs API reference test to stub all cross-origin requests so third-party widgets can’t introduce runtime/network failures.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| packages/playground/website/cypress/e2e/query-api.cy.ts | Replaces a brittle UI selector/assertion with a stable CSS-based check to validate the editor canvas is correctly patched. |
| packages/docs/site/tests/api-reference.spec.ts | Stubs cross-origin requests during the test run to prevent third-party widget fetch failures from breaking the docs build validation. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…onses A bare empty 200 for a script or stylesheet can still make the browser log MIME-type complaints, which the test would then count as errors. Answer scripts and stylesheets with an empty body of the right content type and everything else with 204 No Content.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
CI on trunk has been red since the WordPress 7.1 recompile (a9835e1). Two jobs fail, neither caused by the WP build itself:
test-e2e—query-api.cy.ts › Patching Gutenberg editor frame(both tests). Gutenberg 23.8.0 shipped on 2026-08-19, the same day the job started failing. Block editor: render a real default block in place of the default appender gutenberg#81231 renders a real ghost paragraph instead of the default block appender, so a new post's canvas no longer contains.block-editor-inserter__toggle, and the test times out after 10 minutes waiting for it.test-docs-api-reference—api-reference.spec.ts › loads without runtime errorsfails intermittently onFailed to load resource: 404fromhttps://proxy.kapa.ai/, the third-party assistant widget.Implementation details
overflow-wrap: break-wordon the first.block-editor-block-list__block. That rule comes from block-editor'scontent.cssin every supported WordPress version (verified against 6.8, 7.0, 7.1 and Gutenberg 23.8), the browser default isnormal, and the block list always contains at least the post title block — so the assertion survives the appender change while still proving the canvas frame was patched correctly.page.route('**/*')that answers every cross-origin request with an empty200, so the kapa.ai widget is never fetched and only assets served by the docs build itself are under test.Testing Instructions (or ideally a Blueprint)
test-e2eandtest-docs-api-referenceshould pass on this PR.npx nx e2e playground-website --spec packages/playground/website/cypress/e2e/query-api.cy.tsandnpx nx e2e docs-site.