@raultov/browser-control-mcp 0.8.0-beta.12 → 0.9.0-beta.13

package/CHANGELOG.md

@@ -10,6 +10,63 @@ from a copy of its code: entries describe the differences from that release.
 
 ## [Unreleased]
 
+## [0.9.0-beta.13] - 2026-11-01
+
+Public **BETA**. Frames of another origin are now observed and debugged, not
+only read and acted in: on Chrome their console messages and requests (bodies
+included) join the tab's logs, and on both browsers the debugger searches their
+scripts, binds breakpoints in them and pauses, steps and resumes there.
+Behaviour changes: a click on a disabled control now fails instead of reporting
+success, a pointer action waits up to 2 s for its element to appear or be
+enabled, date, time, range and colour inputs get their value set rather than
+typed, and on Chrome the scripts of such frames have ids naming the frame
+(`2.17`).
+
+### Fixed
+
+- Chrome: `get_console_logs` and `get_network_logs` now include the
+  console messages and requests of frames of another origin (payment forms,
+  widgets, ads), which run in a process of their own and were missing:
+  each tab attaches to its frames as they appear, before their scripts run,
+  and feeds their messages and requests to the tab's logs (at most 50
+  frames per tab). Their response bodies are read from the frame. Firefox
+  already reported them. (#36)
+- Chrome: the debugger now reaches the scripts of frames of another
+  origin. `search_scripts` finds them (their ids name the frame, `2.17`,
+  as each frame numbers its scripts like the page), `set_breakpoint` by URL
+  or hash binds in every frame (also frames that load later, before their
+  scripts run) and by script id in its frame, and a pause in a frame is
+  reported to the call that caused it, inspected, stepped and resumed
+  there. A frame's own `debugger;` statements are skipped without
+  breakpoints, as the page's. (#36)
+- Firefox: the debugger reaches the scripts of frames of another origin too
+  (Firefox runs them in their own process, with their own thread):
+  `search_scripts` finds them, `set_breakpoint` by URL binds in them, and a
+  pause in a frame is inspected, stepped and resumed in its thread. Needs
+  `bidi-lite` 0.1.5 through `bidi-browser-lite` 0.1.6. (#36)
+- Chrome: a click (or any mouse action) into a frame of another origin
+  right after the page loaded was sometimes lost while reported as done:
+  Chrome routes input to such an out-of-process frame only once it has
+  registered it, and until then the parent page got the event on the
+  `<iframe>`. Before the first mouse event into such a frame, the mouse now
+  moves to the point until the frame sees it (at most about 1 s). (#44)
+- `fill_input` and `fill_form` set `date`, `time`, `datetime-local`,
+  `month`, `week`, `range` and `color` inputs: the text was typed into the
+  date's segments (Chrome held `61031-02-02` for `2026-10-31`; Firefox left
+  it empty), and range and colour inputs were refused. The value is now set
+  through the input's native setter, with `input` and `change` events, in
+  the format each type expects (`YYYY-MM-DD`, `HH:MM`, a number,
+  `#rrggbb`); a range that snaps the value to its step or bounds is noted,
+  and a malformed value fails naming the format, leaving the old one. (#38)
+- `click_element`, `drag` and the checkboxes of `fill_form` no longer
+  report success on a disabled control: its click handler never runs, so
+  they now fail with "is disabled; nothing was clicked" and send no input.
+  They also wait up to 2 s for an element a CSS selector does not find yet,
+  or a control that is disabled, as pages add elements and enable buttons a
+  moment after the previous action; the error says how long it waited. A
+  ref that names nothing, a hidden or a covered element still fail at once,
+  and `hover` on a disabled control works as before. (#37)
+
 ## [0.8.0-beta.12] - 2026-10-31
 
 Public **BETA**. Reaches into frames of another origin (payment forms,

package/README.md

@@ -13,7 +13,7 @@ It is the successor of
 from a copy of its code) and complements Playwright MCP or
 chrome-devtools-mcp with runtime JavaScript debugging on both browsers.
 
-> **Status: BETA (0.8.0-beta.12).** This version contains known bugs and differences
+> **Status: BETA (0.9.0-beta.13).** This version contains known bugs and differences
 > between Chrome and Firefox (see [Limitations and TODO](#limitations-and-todo))
 > and parts that have not been verified (see [Untested](#untested)). Tool
 > replies may change in incompatible ways before 1.0. Please report problems
@@ -37,7 +37,7 @@ Tokens are estimated as characters / 4 for every server.
 | Firefox | **✓ next to Chrome, same tools** | ✓ one browser per server | ✗ |
 | Several browsers and instances at once | **✓** | ✗ | ✗ |
 | Selectors | CSS, snapshot refs, `host >>> inner` into shadow roots and iframes | CSS, snapshot refs | snapshot refs only |
-| Frames of another origin (payment forms, embedded editors) | ✓ in the snapshot, refs `f2e5` for every input tool | ✓ refs `f1e5` | ✗ |
+| Frames of another origin (payment forms, embedded editors) | ✓ in the snapshot, refs `f2e5` for every input tool, their console and network in the tab's logs | ✓ refs `f1e5` | ✗ |
 | Snapshot of a long page | **bounded at 50 000 characters**, `find_in_snapshot` searches the rest | unbounded | unbounded |
 | Waits for the page to react after an action | ✓ ~50 ms when nothing reacts | ✓ ~500 ms | ✓ ~200 ms |
 | Clicking a covered or hidden element | **fails at once, naming the overlay** | fails after a 5 s timeout | reports success (the overlay gets the click) |
@@ -129,8 +129,8 @@ see the note.
 | `find_in_snapshot` | ✓ | ✓ | `text` (case-insensitive) or `regex` over the whole outline; matching lines under their ancestors, at most 20 |
 | `save_pdf` | ✓ | ✓ | `files` group; prints the tab as the browser's print does (`landscape`, `print_background`, `scale` 0.1–2, `page_ranges` like `1-3, 5`); with `path` (an absolute `.pdf` under the upload roots) writes the file and answers `{path, bytes, pages}`, else returns the PDF as an embedded `application/pdf` resource (at most 5 MB); Chrome `Page.printToPDF`, Firefox `browsingContext.print` |
 | `capture_screenshot` | ✓ | ✓ | `format` `png`, `jpeg` (or `jpg`) or `webp`; `full_page` at most 16 384 px per side (a text note says when cut); `selector` captures one element (CSS, `host >>> inner` or a snapshot ref), scrolled into view, whole even when taller than the viewport |
-| `click_element` | ✓ | ✓ | scrolls the element into view; `button` (left/right/middle), `click_count` (2 = double click) and `modifiers`; fails without clicking when it is hidden or covered (its own label on top does not count: styled checkboxes and switches are clicked through it; a covered element first gets the mouse, so controls shown only on hover are revealed and clicked); `host >>> inner` selectors reach open shadow roots and same-origin iframes (also in `fill_input`, `scroll`, `wait_for`); a dialog or debugger pause the click causes is noted in a successful reply (`{dialog}` or `{paused, location}`) |
-| `fill_input` | ✓ | ✓ | picks `<select>` options; fails without typing on elements that cannot take the text; `append: true` types after the content instead of replacing it (a number, email or date field, which has no caret, is retyped whole); an editor of its own (an element with an `EditContext` or a focusable `textbox` role, or the hidden input of a code editor such as Monaco or Ace) gets the keys a user presses: a click on the editor when its input has no visible box, Control+A (Command+A on macOS) or Control+End, then the text, and the reply says its content could not be checked; in a contenteditable element (including rich text editors such as Slate, Lexical, ProseMirror or CodeMirror 6) it selects the content (a range, then Control+A as a user would) and types over it, so the editor records the edit; types key by key on both (key handlers run; newlines and tabs inserted as text), about 1 ms per character; `change` on leaving the field, or at the end when the window has no focus |
+| `click_element` | ✓ | ✓ | scrolls the element into view; `button` (left/right/middle), `click_count` (2 = double click) and `modifiers`; fails without clicking when it is hidden, covered (its own label on top does not count: styled checkboxes and switches are clicked through it; a covered element first gets the mouse, so controls shown only on hover are revealed and clicked) or a disabled control, whose handler would never run; an element a CSS selector does not find yet, or a disabled control, is checked again for up to 2 s, as pages add elements and enable buttons a moment after the previous action (a ref that names nothing, a hidden or a covered element fail at once); `host >>> inner` selectors reach open shadow roots and same-origin iframes (also in `fill_input`, `scroll`, `wait_for`); a dialog or debugger pause the click causes is noted in a successful reply (`{dialog}` or `{paused, location}`) |
+| `fill_input` | ✓ | ✓ | picks `<select>` options; sets `date`, `time`, `datetime-local`, `month`, `week`, `range` and `color` inputs to the text in their own format (`2026-10-31`, `13:45`, `72`, `#ff0000`), firing `input` and `change`, noting a value the input adjusted (a range snaps to its step) and failing, without changing it, on a malformed one; fails without typing on elements that cannot take the text; `append: true` types after the content instead of replacing it (a number or email field, which has no caret, is retyped whole); an editor of its own (an element with an `EditContext` or a focusable `textbox` role, or the hidden input of a code editor such as Monaco or Ace) gets the keys a user presses: a click on the editor when its input has no visible box, Control+A (Command+A on macOS) or Control+End, then the text, and the reply says its content could not be checked; in a contenteditable element (including rich text editors such as Slate, Lexical, ProseMirror or CodeMirror 6) it selects the content (a range, then Control+A as a user would) and types over it, so the editor records the edit; types key by key on both (key handlers run; newlines and tabs inserted as text), about 1 ms per character; `change` on leaving the field, or at the end when the window has no focus |
 | `press_key` | ✓ | ✓ | one key (a character, Enter, Tab, Escape, arrows, F1–F12...) with Control / Shift / Alt / Meta held, in `selector` (focused first) or the focused element; a shortcut types nothing |
 | `hover` | ✓ | ✓ | moves the mouse over the element (scrolled into view; fails when hidden or covered) |
 | `drag` | ✓ | ✓ | presses on `from` (checked like `click_element`), moves in steps to the centre of `to` (which must then be in the viewport) and releases: sortable lists, boards, sliders; HTML5 drag and drop is real on Chrome and simulated with script events on Firefox (its WebDriver input starts a native drag but never drops it), and the reply says so |
@@ -154,7 +154,7 @@ see the note.
 | `resume` | ✓ | ✓ | |
 | `step_over` | ✓ | ✓ | |
 | `evaluate_on_call_frame` | ✓ | ✓ | |
-| `search_scripts` | ✓ | ✓ | a long line's preview is 100 characters on each side of the match |
+| `search_scripts` | ✓ | ✓ | a long line's preview is 100 characters on each side of the match; frames of another origin too (Chrome ids such as `2.17`) |
 | `pause_on_load` | ✓ | ✗ | TODO on Firefox, see [Limitations and TODO](#limitations-and-todo) |
 | `enable_proxy_auth` | ✓ | partial | needs `--proxy-server`; a request the proxy rejects twice is cancelled; untested on Firefox against a real proxy |
 | `send_cdp_command` | ✓ | ✗ | `raw` group; raw Chrome DevTools Protocol; refuses `Network`/`Page`/`Runtime`/`Log`/`Debugger.disable` and `Browser.close`; `Fetch.enable` comes with a note |
@@ -623,7 +623,11 @@ incompatible:
 - Frames of another origin: `evaluate_js` runs in the page only, and
   `capture_screenshot` cannot clip to an element inside such a frame (pass
   the iframe's ref instead); `snapshot` reads at most 20 of them, 5 deep;
-  the coordinates in the replies of the input tools are the frame's.
+  the coordinates in the replies of the input tools are the frame's. On
+  Chrome, the console and network of at most 50 of them per tab are
+  logged, and the debugger reaches their scripts (ids such as `2.17`:
+  frame 2's script 17), as it does on Firefox; `pause_on_load` pauses the
+  page only.
 
 ## Untested
 

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@raultov/browser-control-mcp",
-      "version": "0.8.0-beta.12"
+      "version": "0.9.0-beta.13"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.8.0-beta.12"
+  "version": "0.9.0-beta.13"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/raultov/browser-control-mcp/releases/download/v0.8.0-beta.12"
+    "https://github.com/raultov/browser-control-mcp/releases/download/v0.9.0-beta.13"
   ],
   "author": "raultov <raultov@protonmail.com>",
   "bin": {
@@ -92,7 +92,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.8.0-beta.12",
+  "version": "0.9.0-beta.13",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"