You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5713011 test(T-10957): instant_element_wait is the one home for zeroing the element waits (five file-local copies folded in); the zero-timeout test pins CDP_OPERATION_TIMEOUT itself (review of 15ca5d2: LOW x2)
82d81a9 test(T-10957): hermetic cloner tests no longer sit out the 10 s selector wait or the 30 s CDP default
63cee10 test(T-10848): the close_tab tool clears the caller-owned mark on the browser it closed (review of fdcd718: MED)
943c3a9 fix(T-10848): close_tab clears the caller-screencast mark on its live browser (re-review of 453ad1b)
b41c221 fix(T-10848): caller-owned screencast ids live on the tab's browser, so they go with it on close, crash and relaunch (Opus review of 5043478)
914b198 fix(T-10848): a screencast tab closed any way but close_tab leaves paint_hold's caller-owned set (browser closed or target destroyed)
888f0a4 fix(T-11043): pin the departure fingerprint on the chain click_element really builds (ToolError>ToolError>departure), state it in the CHANGELOG, and a cause whose text cannot be read is not a departure (Opus review of dcec80b)
ca89c2c fix(T-11043): an element that left the page is one Sentry issue whichever way Chrome said so; the fingerprint asks detached_element and names one cause (-EY 12 events, -EZ 3 under 2.1.54)
dd0fbbc fix(T-9478): a resource_type validates and matches by one lookup (CDP value or member name, any case); null is no filter; the paused event is read through resource_type_of
2717c15 test(T-9478): E2E shows a hook naming the type Chrome reports fulfills a real fetch; the paused-event path and the CHANGELOG say XHR
05ab6a1 fix(T-9478): a bad resource_type in a dynamic hook is a CallerError naming the valid types, raised before the hook is stored; create_hook logs once; a resource_type requirement now matches
b05a502 test(T-10841): the grace test pins the back-date the product writes, so a product that stops back-dating (or back-dates by another amount) fails it
ac5704a test(T-10841): the failed-launch grace test ages its marker from the clock at the check, not from a stale mtime; a 2.2 s gap between write and check is pinned
a724f82 docs(T-9675): the entry goes under Unreleased, not the 2.1.54 it merged into (rebase onto 8dd893b)
8de76e0 test(T-9675): a child that exits as the deadline kill lands is read once more, not an error (Opus review of 24077eb: LOW)
706499d test(T-9675): the boot-log wait checks the child's identity, kills a stuck child, retries a transient read error, and is shared with test_backend_launch
82082c3 test(T-9675): the boot-crash test waits for the child's output or exit, not a fixed 10 s window
f74c4c3 test(T-9551): the spawn-budget Browser double lists its pages as nodriver's Browser.tabs does, since spawn now reads them through tab_open.initial_tab
d566eed test(T-9551): the every-version forwarder close test runs under a 0.3 s budget, so its margin is several times the budget on a slow runner (Opus review of b06a594: LOW)
9145156 test(T-9551): the forwarder's open-client close test is valid below Python 3.13; browser_connect's leaf note names tab_open
63be988 fix(T-9551): the re-attach keeps nodriver's pick unless it is Chrome's own tab; spawn reads the same helper; the forwarder's close is bounded
a7d4ae1 fix(T-9551): a re-attach adopts the original page, not the newest tab; a cancelled close still closes the proxy forwarder