New: the context option WithRuntimeDisabled attaches to the target without Runtime.enable. While the Runtime domain is enabled, Chrome prepares each argument of a console call for the protocol, so a page can tell that a program drives it. With the option, the queries and Poll run in an isolated world of each frame, which sees the DOM and not the globals of the page. Evaluate still runs in the main world. Chrome sends no Runtime events, so Console, Listen, Events and WithListener get none, and ExposeFunc returns an error that wraps the new ErrRuntimeDisabled. See example 31 in docs/API.md and docs/decisions/2026-11-18-attach-with-the-runtime-domain-disabled.md.
Fix: a Poll in a frame could hang, because runPoll took the read lock of frameMu twice.
Dušan Panić proposed the option and found the hang in discussion #1647.