Repository navigation
popup e2e: mobile-WebKit hop out of isolation sometimes never loads (CI only) #121
Description
e2e/popup.spec.ts › "[POPUP-CONTROL-002] [POPUP-CONNECTION-003] [POPUP-KEEPER-003] one port survives app-driven navigation into and out of isolation" failed once on [mobile-webkit]. That was run 38252996362, attempt 1, on main at 7b929b6.
- The app-driven hop into isolation (
/isolated) loads, and its pong confirmsisolated: true. - The hop back out (
navigate(page, '/p#c=…')) never produces the next document:page.waitForEvent('domcontentloaded')times out after 15 s. - Attempt 2 passed this test. It failed popup: mobile-WebKit flake in close-right-after-navigate (CI only) #86 instead, which is also a WebKit navigation through the kept port, so the two may share a cause.
Trace: artifact traces-popup-webkit, id 11748782918, from attempt 1 (gh api repos/libid-org/libID/actions/artifacts/11748782918/zip > traces.zip).
Activity
test(popup): retry WebKit browser tests once
Wondertan commentedon Oct 12, 2026
Root cause is a WebKit bug: a navigation that switches browsing context group (COOP) sometimes never commits. It reproduces with two plain pages, in stock WebKitGTK too. Reported upstream: https://bugs.webkit.org/show_bug.cgi?id=327297. A product-side re-navigation retry made this test fail more often, so #128 retries the WebKit browser tests instead.
fix(popup): navigate again when WebKit stalls a hop, keeping its port
fix(popup): navigate again when WebKit stalls a hop, keeping its port
fix(popup): navigate again when WebKit stalls a hop, keeping its port
fix(popup): navigate again when WebKit stalls a hop, keeping its port