Skip to content

v0.12.1

Choose a tag to compare

@sheehanmunim sheehanmunim released this 06 Nov 05:14
· 20 commits to main since this release

Browser: pages Chrome is not drawing no longer read as empty (#63, #64)

A signed-in Fathom recording page came back from browser_snapshot with total=0 and from browser_read with no text, even though its title updated. Fathom's page is built from web components that stay hidden until the page draws its first frame. Chrome draws no frames for a tab it isn't showing (an inactive tab, or one whose window is minimized or covered), so the whole page looked empty.

v0.12.0 already has Chrome treat the agent's tabs as shown, which makes such a page draw at once on macOS and Windows. This release covers the cases where that isn't enough, and makes an undrawn page say so instead of looking empty:

  • Pages get a frame first. After the extension attaches to a tab, it gives the page up to two frames (300 ms at most), so a page that loaded hidden can finish showing itself before the first read.
  • One retry. When browser_snapshot, browser_read or wait_for_selector finds nothing on a page that reports itself hidden, it asks Chrome again to show the tab, waits for a frame and looks once more.
  • An empty result says why. If the page still isn't drawn, the snapshot, the read and a selector-wait timeout say Chrome is not drawing this tab and tell you to restore or uncover its Chrome window, instead of total=0 or (no readable text on this page). An empty read of a page that is drawn says how much text the page holds but hides with CSS.

34 tools on every platform. Update the Chrome extension too: reload the unpacked extension or install the new munim-computer-use-chrome-extension.zip. The fix lives in the extension.