323386 2026-09-03 16:58:00 -0700 WebDriver reports "stale element reference" for a node reference from a different browsing context 2026-09-08 14:44:36 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=323695 https://bugs.webkit.org/show_bug.cgi?id=230612 https://bugs.webkit.org/show_bug.cgi?id=323692 https://bugs.webkit.org/show_bug.cgi?id=323694 InRadar P2 Normal --- 1 bfulgham bfulgham lmoura webkit-bug-importer oldest_to_newest 2247102 0 bfulgham 2026-09-03 16:58:00 -0700 Each frame's injected WebAutomationSessionProxy.js keeps its own map of node handles. _nodeForIdentifier() throws NodeNotFound whenever a handle is absent from that map, which conflates two different situations: (1) the node was in this frame and has since been detached (a stale handle) (2) the node was never in this frame, because it belongs to a different frame or window CommandResult.cpp maps NodeNotFound to StaleElementReference, so both report stale element reference. Per the spec the second case is no such element (or no such shadow root for a shadow root reference). _clearStaleNodes() already knows the difference: it evicts exactly those handles whose node is no longer rooted in this document. Recording what it evicts lets _nodeForIdentifier() throw a distinct StaleNode error for the detached case and keep NodeNotFound for the foreign one. This fix improves 16 subtests across webdriver/tests/classic/execute_script/arguments.py and execute_async_script/arguments.py 2247103 1 webkit-bug-importer 2026-09-03 16:58:21 -0700 <rdar://problem/186615759> 2247108 2 bfulgham 2026-09-03 17:07:22 -0700 Pull request: https://github.com/WebKit/WebKit/pull/73206 2247337 3 ews-feeder 2026-09-04 09:33:37 -0700 Committed 320518@main (f56eb24b3195): <https://commits.webkit.org/320518@main> Reviewed commits have been landed. Closing PR #73206 and removing active labels. 2248309 4 lmoura 2026-09-08 14:44:36 -0700 (I had edited the wrong field, sorry)