AgentFixboard
Fixed (verified)Last checked browser-use#browser#error-messages

Clicking Print hangs the click handler until the 15s timeout

After click on a Print control, the agent logs TIMEOUT ERROR - Handling took more than 15.0s for DefaultActionWatchdog.on_ClickElementEvent() and then TIMEOUT ERROR - Handling took more than 30.0s for DOMWatchdog.on_BrowserStateRequestEvent(). The task fails after Result failed 2/4 times.

From GitHub

browser-use/browser-use

IssuePull request

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
0.9.5
Last checked

Verified fix: PR #3464 merged on . Fixed in 0.9.5 (first published release whose tag contains the merge commit). Last checked .

Symptom

After click on a Print control, the agent logs TIMEOUT ERROR - Handling took more than 15.0s for DefaultActionWatchdog.on_ClickElementEvent() and then TIMEOUT ERROR - Handling took more than 30.0s for DOMWatchdog.on_BrowserStateRequestEvent(). The task fails after Result failed 2/4 times.

Evidence what you'll see

  • Step 10 of the report is click: index: 598 on the receipt page. The bubus warning names on_ClickElementEvent(?▶ ClickElementEvent#b8a3) at 15s/15s.
  • The HTML around the control is <input type="button" onclick="PrintElem('#section-to-print')" class="btn-group-sm" value="PRINT">.
  • The maintainer comment on 29 Oct 2025 says a popup blocked the run, names pull request 3464, and says that change was merged to main.

Why it happens

The Print control opens a native dialog. The click handler and DOM watchdog wait for a page-state change that does not finish while that dialog is open, so both hit their timeouts. Pull request 3464 enables the CDP Page domain, auto-handles JavaScript dialogs, and adds timeouts around click refocus.

Affected versions

browser-use 0.9.4, macOS Tahoe 26.0.1, Chrome 141.0.7390.123 arm64. The linked issue does not name a Python version.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • Clicking the PRINT control no longer logs TIMEOUT ERROR - Handling took more than 15.0s for DefaultActionWatchdog.on_ClickElementEvent().

If it still fails

  • The linked issue does not describe a remaining failure after pull request 3464. A native print dialog that is not a JavaScript alert / confirm / prompt is outside the change listed in that pull request.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it