fix(firefox): use bypassServiceWorker flag for storage state pages

[Dmitry Gozman (dgozman)]

References #42656.

[github-actions]

Test results for "tests 1"

7 flaky

⚠️ [chromium-page] › page/page-history.spec.ts:94 › goBack/goForward should work with bfcache-able pages `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/video.spec.ts:736 › screencast › should work with video+trace `@realtime-time-library-chromium-linux`
⚠️ [chromium-library] › library/video.spec.ts:356 › screencast › should work for popups `@chromium-ubuntu-22.04-node20`
⚠️ [chromium-library] › library/video.spec.ts:736 › screencast › should work with video+trace `@chromium-ubuntu-22.04-node22`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:257 › third party 'Partitioned;' cookies `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:470 › top level 'Partitioned;' cookie and same origin iframe `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-page] › page/page-event-request.spec.ts:181 › should return response body when Cross-Origin-Opener-Policy is set `@firefox-ubuntu-22.04-node20`

51721 passed, 1247 skipped

---

Merge workflow run.

[github-actions]

Test results for "MCP"

1 failed
❌ [firefox] › mcp/cli-session.spec.ts:54 › idle timeout shuts the session down @mcp-windows-latest-firefox

8563 passed, 1446 skipped

---

Merge workflow run.

[github-actions]

🟢 The one failure is a known pre-existing flake — this PR looks clear

Hi, I'm the Playwright bot and I took a look at the failing CI.

[firefox] › mcp/cli-session.spec.ts:54 › idle timeout shuts the session down on @mcp-windows-latest-firefox fails with the same Expected substring: "(no browsers)" assertion on main and on a dozen unrelated PRs — including commit 1820528, which is this PR's own base. It has failed 16 of 47 runs (34%) on that bot, and never once on any of the other 12 MCP bots.

Details

Pre-existing flake / infra

• [firefox] › mcp/cli-session.spec.ts:54 › idle timeout shuts the session down (@mcp-windows-latest-firefox) — flips verdict across runs on SHAs this PR can't be responsible for: pushes to main d1ead3e, 654654f, 52a0e72, a024162, 9ae5377, 1820528, and PRs feat(coverage): experimental istanbul coverage collection via tracing #42684, test: roll stable-test-runner to 1.64.0-alpha-2026-09-14 #42706, feat(mcp): add --file-paths=absolute for absolute paths in tool results #42673, test: fix click tests on android #42726, fix(network): preserve dates in response headers #42734, fix(mcp): do not close browser while tool call is running #42696, feat(firefox): roll to r1546 #42735, test: evaluate() with falsy result #42728. Every failure is the identical assertion on the session-list output, so it reads as a Windows-only timing race between the idle shutdown and the CLI listing, not a product regression.

  Run history on that bot, oldest first — 🟩🟩🟩🟩🟩🟥🟩🟥🟥🟥🟩🟥🟥🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟥🟩🟩🟩🟥🟩🟥🟥🟥🟥🟩🟩🟩🟩🟥🟥🟩🟥🟥

  The diff also doesn't reach it: the change is three lines threading bypassServiceWorker through ffNetworkManager.setRequestInterception, which only takes effect for storage-state pages with request interception on. The MCP session idle-timeout test exercises neither.

The 7 flaky tests in "tests 1" all passed on retry and none of them touch Firefox request interception or storage state, so there's nothing to triage there.

_{Triaged by the Playwright bot - agent run}