fix(browser): route page-scoped keyboard input through CDP - #13231
fix(browser): route page-scoped keyboard input through CDP#13231innocarpe wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe browser bridge now uses direct CDP operations for text input and keypresses. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: ee5e5969-a8ba-49cb-b282-dfbd999c576c
📒 Files selected for processing (2)
src/main/browser/agent-browser-bridge.test.tssrc/main/browser/agent-browser-bridge.ts
e790637 to
0412a3b
Compare
Sync update (
|
Description
Browser
typeandkeypresscommands now deliver page-scoped input to the requested browserwebContentsinstead of the OS-focused window.The bridge uses direct CDP input dispatch for targeted pages and reports success only after the target page accepted the command.
Focused fix
--pagefor focus-based browser text and key input, including chunked text insertion.Preserves
Evidence
pnpm exec vitest run --config config/vitest.config.ts src/main/browser/agent-browser-bridge.test.tsUser-regression-tradeoffs
Fixes #12912