diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-13 02:35:01 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-13 02:35:01 -0400 |
| commit | 26ab0d36e45b1b65f667d4743eb30e83389ff57f (patch) | |
| tree | 678f92867c16671caa116b4e1762a672703f9863 /test-suite/notes | |
| parent | b319c82a75e9a6488a6454790d1436f74a655e7c (diff) | |
pi-chrome 0.14.2: recover from foreign-extension input overlays
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.
Diffstat (limited to 'test-suite/notes')
| -rw-r--r-- | test-suite/notes/bypass-ideas.md | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/test-suite/notes/bypass-ideas.md b/test-suite/notes/bypass-ideas.md index 7a019b6..7980aaa 100644 --- a/test-suite/notes/bypass-ideas.md +++ b/test-suite/notes/bypass-ideas.md @@ -1,9 +1,12 @@ -# What it would take to PASS each challenge +# Historical bypass notes -`pi-chrome` runs through a content-script bridge, not CDP. That limits the -solution space — most "real-event" tricks need the chrome.debugger API or -`chrome.input.synthesizeMouseEvent`. The notes below mark which are reachable -with the current manifest and which require new permissions. +This file predates the current `trusted:true` / `chrome.debugger` path and is +kept as design history. For current benchmark expectations, recipes, and +capability notes, use `../manifest.json`. + +Older context: `pi-chrome` originally ran mostly through a content-script bridge. +That limited the solution space — most "real-event" tricks needed the +`chrome.debugger` API or `chrome.input.synthesizeMouseEvent`. ## 01–02 isTrusted click / keyboard **Hard.** `Event.isTrusted` is true only for events the browser dispatched |