docs(report): note the file: protocol block in Path A (Playwright MCP)#77
Merged
Merged
Conversation
@playwright/mcp blocks file:// URLs by default, so the documented `browser_navigate file://…/validation-report.html` step fails. Add the verified workaround (serve the output dir over a throwaway local HTTP server) plus a note that the saved PNG lands in the MCP server's cwd. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Adds a caveat to
docs/validation-report.md§10 Path A documenting that@playwright/mcpblocks thefile:protocol by default — so the documentedbrowser_navigate file://…/validation-report.htmlstep fails with "Access to 'file:' protocol is blocked."Why
Hit this empirically while running Path A to visually verify a
validation-report.html. The doc as written can't be followed literally. The fix documents the verified workaround (serve the output dir over a throwaway localpython3 -m http.serverand navigate tohttp://127.0.0.1:<port>/…), notes that the self-contained report needs only a plain static server, and flags thatbrowser_take_screenshot's saved PNG lands in the MCP server's cwd (project root), not the output dir.Scope
Docs only — one paragraph + a code block. No code, no pipeline change.
🤖 Generated with Claude Code