@btraut/browser-bridge 0.7.2 → 0.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +15 -1
- package/README.md +8 -0
- package/extension/dist/background.js +725 -8
- package/extension/dist/background.js.map +3 -3
- package/extension/dist/content.js +85 -0
- package/extension/dist/content.js.map +2 -2
- package/extension/manifest.json +1 -1
- package/package.json +1 -1
- package/skills/browser-bridge/skill.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -6,7 +6,21 @@ The format is based on "Keep a Changelog", and this project adheres to Semantic
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
## [0.8.0] - 2026-02-14
|
|
10
|
+
|
|
11
|
+
### Changed
|
|
12
|
+
|
|
13
|
+
- `drive.click` now dispatches deferred clicks through CDP `Input.dispatchMouseEvent` in the extension background path, with locator point resolution coming from the content script.
|
|
14
|
+
- `drive.hover` and `drive.drag` now run through CDP mouse movement/press/release events in the extension background path, with HTML snapshot capture handled as a separate internal content action.
|
|
15
|
+
- `drive.key`, `drive.key_press`, and `drive.type` now route through CDP keyboard/text input commands in the extension background path, while content script target helpers only resolve/validate editable targets.
|
|
16
|
+
- `drive.select` and `drive.fill_form` now run CDP-backed focus/typing primitives first, with explicit content-script fallback for control-specific operations that CDP does not map directly.
|
|
17
|
+
- Added `docs/cdp-input-model.md` plus stronger assertions in `scripts/cli-full-tool-smoke.sh` to validate focus/value/drag side effects during CDP-input smoke runs.
|
|
18
|
+
|
|
19
|
+
## [0.7.3] - 2026-02-14
|
|
20
|
+
|
|
21
|
+
### Fixed
|
|
22
|
+
|
|
23
|
+
- `drive.click` now focuses the target element before dispatching the deferred click, so clicking inputs updates `document.activeElement` as expected.
|
|
10
24
|
|
|
11
25
|
## [0.7.2] - 2026-02-12
|
|
12
26
|
|
package/README.md
CHANGED
|
@@ -82,6 +82,14 @@ What makes it different:
|
|
|
82
82
|
- **Recovery-first**: sessions have an explicit state machine with `session.recover()` and `diagnostics doctor`.
|
|
83
83
|
- **Inspect beyond screenshots**: DOM snapshots (AX + HTML) and `inspect dom-diff` to detect page changes.
|
|
84
84
|
|
|
85
|
+
## Input Semantics
|
|
86
|
+
|
|
87
|
+
Drive input actions are CDP-first (Chrome DevTools Protocol `Input.*`) so click, hover, drag, key, and type behavior follows Chrome's native input pipeline instead of synthetic DOM event dispatch.
|
|
88
|
+
|
|
89
|
+
High-level helpers (`drive.select`, `drive.fill_form`) still use explicit fallback branches for control-specific operations that CDP does not model directly (for example selecting by option value/text/index).
|
|
90
|
+
|
|
91
|
+
See `docs/cdp-input-model.md` for details and smoke verification.
|
|
92
|
+
|
|
85
93
|
## 🆚 Feature Comparison
|
|
86
94
|
|
|
87
95
|
| Category | Browser Bridge | Playwright MCP | agent-browser | mcp-chrome | Claude Code + Chrome |
|