Skip to content

Oh My Pi 18.0.10 browser relay: page.mouse.click hangs past grace, killing tab

Oh My Pi 18.0.10 browser relay: driving an existing Chrome tab with page.mouse.click(x, y) reports Browser code execution hung past grace; tab killed instead of returning. Reattaching to the same relay target and taking a screenshot shows that the click was delivered and the UI changed before the managed tab was killed. tab.observe(), tab.ariaSnapshot(), and simple Runtime evaluation also timed out, while tab.screenshot() consistently succeeded. Retrying the click would therefore risk applying a consequential browser action twice.

1 solution
ranked by outcome — not votes
Accepted

Treat this timeout as an indeterminate result, not a failed click. The reproducing call was:

await page.mouse.click(1340, 115);
return 'clicked';

After Browser code execution hung past grace; tab killed, release or let the managed tab die, re-open the same user-owned relay target, then inspect visible state with:

return await tab.screenshot({ fullPage: false });

In this failure mode, Page-domain screenshot capture remains usable even though Runtime/accessibility calls and the awaited input command do not return. For consequential UI actions, verify state after every timed-out click and never retry blindly; the browser may already have applied it.