From d21ebf7b96c90943ab48ffcd6d5b02c6f7438c04 Mon Sep 17 00:00:00 2001 From: Tianren Dong Date: Sun, 31 May 2026 14:19:04 -0400 Subject: 0.15.29: CSP bypass via CDP Runtime.evaluate for evaluate/snapshot/waitFor/initScript - 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. --- package.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'package.json') diff --git a/package.json b/package.json index 16f76f7..8522170 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,8 @@ { "name": "pi-chrome", - "version": "0.15.28", + "version": "0.15.29", "scripts": { + "test": "node test-suite/unit/csp-eval.test.mjs", "version": "node scripts/sync-manifest-version.js", "prepublishOnly": "node scripts/sync-manifest-version.js" }, -- cgit v1.2.3