Fix editor canvas probe authentication - #2510
Merged
Merged
Conversation
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.
Summary
wordpress.editor-canvas-probenavigates to an editor targetRoot cause
The probe resolved
target=front-pageto/wp-admin/post.php, but unlike the other editor commands it launched a fresh browser without installing WordPress auth cookies. Real runs redirected away from the editor and timed out withiframe-missing.Verification
npm run test:browser-routed-command-securitynpm run buildeditor-openfound one canvas iframe and 474/474 valid blocks; the unauthenticated probe alone failedAI assistance
OpenAI GPT-5.6 Sol via OpenCode analyzed the retained CI browser artifacts, isolated the missing authentication call, implemented the focused fix, and ran the verification above. Chris Huber reviewed and orchestrated the work.