Skip to content

0.9.2

Choose a tag to compare

@sheehanmunim sheehanmunim released this 31 Oct 15:53

Fixes

  • Browser: indexed browser_click presses like a real mouse (#42). It used to play the press as page events with buttons: 0 and no pointer type, then el.click() with a click count of 0, so controls that check the press state (Gmail's message options menu, per the report) could ignore it.

    • Tab on screen: the click is now real input through Chrome's DevTools pipeline (trusted events). The hover is checked to land on the element before anything is pressed, so a point the page reads differently (zoom, a layout shift) never presses something else. A press that did not arrive falls back once, and a press that navigated is never repeated.
    • Background tab: Chrome drops real input here, so the press is still played as page events, now with a real press's metadata: buttons: 1 on press, pointerType: 'mouse', click count 1, and a cancelled pointerdown/mousedown behaving as it does for a real mouse.
    • Click result: names the element and the route, e.g. clicked in tab 5 — [12] button "More message options", with real mouse input or … as page events (the tab is in the background). This tells a stale index apart from an ignored press.

    Thanks @ElliotDrel for the precise report.

Tested live

  • Chrome (Chrome for Testing 156, extension e2e): a menu that opens only for buttons === 1 opens from a background tab (page events) and from a shown tab (trusted input, isTrusted: true); the existing 18 browser checks pass.
  • Windows 11: Calculator by element clicks, run_steps, screenshot.
  • macOS (universal, Developer ID signed): Calculator by element clicks, run_steps, screenshot.
  • Linux (Xvfb + bspwm, X11): Calculator by element clicks, run_steps, screenshot; screenshot mapping at Xft.dpi: 144.