From 40c14a84dac7b6d56920eefda2c4b659630e1a18 Mon Sep 17 00:00:00 2001 From: Tianren Dong Date: Wed, 13 May 2026 01:58:25 -0400 Subject: pi-chrome 0.11.4: drop 'yellow' from banner copy; quote exact banner text MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Banner is themed by the user's Chrome (dark mode → dark grey for many users), not always yellow. Use 'banner' alone or quote the actual banner text 'Pi Chrome Connector started debugging this browser'. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 82468bf..8acd598 100644 --- a/README.md +++ b/README.md @@ -69,7 +69,7 @@ pi-chrome v By default, `chrome_*` clicks and keystrokes are **synthetic** DOM events (`event.isTrusted === false`). They drive React/Vue/Angular state correctly but **do not** satisfy Chrome's user-activation gates: clipboard write, fullscreen, file picker, and autoplay all need a real user gesture. -pi-chrome can optionally route input through `chrome.debugger` (CDP `Input.dispatchMouseEvent` / `Input.dispatchKeyEvent`) so each event arrives as `isTrusted=true`, satisfies user-activation, and bypasses site bot-detection that filters synthetic events. The tradeoff: Chrome pins a yellow *"Pi Chrome Connector started debugging this browser"* banner to the top of any debugged tab. +pi-chrome can optionally route input through `chrome.debugger` (CDP `Input.dispatchMouseEvent` / `Input.dispatchKeyEvent`) so each event arrives as `isTrusted=true`, satisfies user-activation, and bypasses site bot-detection that filters synthetic events. The tradeoff: Chrome pins a *"Pi Chrome Connector started debugging this browser"* banner to the top of any debugged tab. Usage: -- cgit v1.2.3