Repository navigation
docs(cables-relay): update verification status with real browser-automation findings - #11
Merged
Merged
Conversation
…mation findings The "not tested against real cables.gl" caveat was written before live browser automation against the actual cables.gl editor (real op class confirmed, real DOM field editing verified). Replace it with what was actually proven, and name the real blocker found afterward — Chrome's Local Network Access policy blocking a public-origin page from reaching localhost, not a defect in the relay or in cables. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Follow-up to the previous commit on this branch, which documented that a round-trip wasn't completed yet. It now is: driven end to end against the real public cables.gl editor, the live WebSocket_v2 op showed Connected/Valid JSON/Raw Data with this relay's real DENY payload, reproduced twice. Records exactly what unblocked it (Chromium feature flags, not a permission grant) and what's still unconfirmed (whether a real user's interactive permission prompt behaves the same way). Co-Authored-By: Claude Sonnet 5 <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
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
tools/cables-pchi-relay/README.mdwith what live browser automation actually proved: the real op class (Ops.Net.WebSocket.WebSocket_v2) confirmed in a live, currently-maintained example patch, its canvas located inside cables' separate-originsandbox.cables.gliframe, and its URL field genuinely read and edited through cables' own UI.Connected: true,Valid JSON: true, and aRaw Datavalue carrying the realgate_state: "DENY"payload. Reproduced twice.net::ERR_BLOCKED_BY_LOCAL_NETWORK_ACCESS_CHECKS). Granting thelocal-network-accesspermission programmatically did not clear it; disabling Chromium'sLocalNetworkAccessChecks/LocalNetworkAccessChecksWebSocketsfeature flags at browser launch did. Both are automation-only levers, so the README is explicit that this isn't confirmed to match what a real visitor clicking through Chrome's actual interactive prompt would experience — with cables' own standalone/Electron build noted as the clean production path around the whole question.Test plan
main's README (clean, no conflicts with cables.gl PCHI relay — HTTP/WebSocket translation for a browser-sandboxed tool #10's content)🤖 Generated with Claude Code