sz-chrome-remote-extension.git/test-suite/manifest.json, branch masterpi-chrome, patched to drive a signed-in browser on another host through a broker, with an MCP server
https://git.soarez.net/sz/sz-chrome-remote-extension.git/atom?h=master2026-09-10T13:57:16+00:00Improve Chrome input reliability and release 0.15.492026-09-10T13:57:16+00:00Tianren Dongtianrendong.dtr@gmail.com2026-09-10T13:31:19+00:00urn:sha1:ec23b553a245d3d57f428d03002ed77a785d300aEnforce hard background and release 0.15.482026-09-10T03:48:50+00:00Tianren Dongtianrendong.dtr@gmail.com2026-09-10T03:37:02+00:00urn:sha1:c1f230eeb76aaa50e98d3fe7d838573612b6e36f0.15.29: CSP bypass via CDP Runtime.evaluate for evaluate/snapshot/waitFor/initScript2026-05-31T18:19:04+00:00Tianren Dongtianrendong.dtr@gmail.com2026-05-31T18:19:04+00:00urn:sha1:d21ebf7b96c90943ab48ffcd6d5b02c6f7438c04
- evaluateInTab/executeInTab now run through CDP Runtime.evaluate instead of
new Function() in MAIN world, so chrome_evaluate/chrome_snapshot work on pages
that block unsafe-eval (github.com, many bank/SaaS apps). Preserves value
markers (undefined/function/symbol/bigint/Error), DOMRect expansion, and the
expression/statement fallback; keeps {ok,value} error envelope.
- page.waitFor polls via service-worker-side CDP evaluation.
- chrome_navigate initScript uses Page.addScriptToEvaluateOnNewDocument.
- Add npm test (test-suite/unit/csp-eval.test.mjs) and in-browser regression
challenge 42 strict-csp-evaluate; update challenge 39 notes + docs/primer.
0.15.25: fix reload after stale singleton2026-05-16T18:01:00+00:00Tianren Dongtianrendong.dtr@gmail.com2026-05-16T18:01:00+00:00urn:sha1:b792f22f2c2ef4dfb7bd300e7381a186e34e0c18pi-chrome: snapshot pre-migration state2026-05-13T11:29:41+00:00Tianren Dongtianrendong.dtr@gmail.com2026-05-13T11:29:41+00:00urn:sha1:4c54b05dc15b81e449dc8ac53da8bae536fa2798pi-chrome 0.14.2: recover from foreign-extension input overlays2026-05-13T06:35:01+00:00Tianren Dongtianrendong.dtr@gmail.com2026-05-13T06:35:01+00:00urn:sha1:26ab0d36e45b1b65f667d4743eb30e83389ff57f
When a different Chrome extension (password manager, autofill popup,
etc.) anchors an overlay to the focused input, Chrome's CDP refuses
our Input.dispatchMouseEvent with 'Cannot access a chrome-extension://
URL of different extension'. The CDP target list shows the foreign
chrome-extension:// URL as type:'other' attached to the same tab.
New behaviour in cdp() wrapper:
1. On that specific error for any Input.* call, snapshot CDP targets
to identify the offending extension id and log it (foreign-ext-
detected event added to ring buffer).
2. Send Esc via Input.dispatchKeyEvent (key dispatch routes by focus,
not coordinates, so it bypasses the overlay) to dismiss the popup.
3. Retry the original Input.* call once.
4. If retry still fails, throw a clear error naming the foreign
extension id and listing three concrete workarounds: disable that
extension on the page, use Tab-to-focus instead of clicking, or
run /chrome quiet off.