docs: isMobile is supported in Firefox since v1.61

[Yury Semikhatsky (yury-s)]

Summary

• Drop the stale "not supported in Firefox" note from the isMobile option docs; Firefox mobile mode shipped in feat(firefox): support mobile mode #41179 (v1.61).

Fixes #42835

[github-actions]

Test results for "tests 1"

9 flaky

⚠️ [chromium-library] › library/beforeunload.spec.ts:130 › should support dismissing the dialog multiple times `@frozen-time-library-chromium-linux`
⚠️ [chromium-library] › library/video.spec.ts:690 › screencast › should capture full viewport `@frozen-time-library-chromium-linux`
⚠️ [chromium-library] › library/browsercontext-page-event.spec.ts:173 › should work with Ctrl-clicking `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/video.spec.ts:762 › screencast › should work with video+trace `@realtime-time-library-chromium-linux`
⚠️ [chromium-library] › library/video.spec.ts:690 › screencast › should capture full viewport `@chromium-ubuntu-22.04-node20`
⚠️ [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`
⚠️ [webkit-page] › page/page-autowaiting-basic.spec.ts:58 › should await form-get on click `@webkit-ubuntu-22.04-node20`
⚠️ [webkit-page] › page/page-leaks.spec.ts:136 › expect should not leak `@webkit-ubuntu-22.04-node20`

52036 passed, 1244 skipped

---

Merge workflow run.

[github-actions]

Test results for "MCP"

1 failed
❌ [chromium] › mcp/cli-webmcp.spec.ts:188 › webmcp-call disambiguates same-name tools in identical same-origin frames @mcp-macos-latest-chromium

8691 passed, 1474 skipped

---

Merge workflow run.

[github-actions]

🟢 CI is clear — the one failure is a known flake

Hi, I'm the Playwright bot and I triaged the red CI here. The only failing test is mcp/cli-webmcp.spec.ts:188, and it fails the same way on plenty of SHAs this PR can't be responsible for.

Details

This PR is docs-only — docs/src/api/params.md plus the regenerated types.d.ts files. No product code path is touched, and nothing in the MCP frame-disambiguation flow reads those files.

Pre-existing flake / infra

• [chromium] › mcp/cli-webmcp.spec.ts:188 › webmcp-call disambiguates same-name tools in identical same-origin frames (@mcp-macos-latest-chromium) — pre-existing flake. In the aggregated CI results this test flips verdict across runs on unrelated SHAs: failed on PRs chore(coverage): istanbul instrumentation for the trace viewer and html reporter #42785 (fabe18a1), test(firefox): cover COOP navigation with history state #42788 (1f166c07), fix(skills): narrow npm and npx grants #42789 (3f0fa945), feat(test-runner): support locks in test.describe.configure #42792 (67318a99), fix(firefox): preserve response header field boundaries #42832 (f61c51d2), docs(cli): do not suggest generating test scenarios in parallel #42833 (478ae0a1) and on a push build (07f1a615) — 8 failures in ~273 runs, passing the rest. It fails on both macOS and Ubuntu and on both the chrome and chromium projects.

  The error is always the same shape, and the expectation itself is what shifts:

  Expected substring: "- frame: http://localhost:8907/widget.html (frame 1)"
  

  …except some runs expect (frame 2). The two identical same-origin frames aren't attached in a deterministic order, so the disambiguation suffix swaps between runs — a race in the test/fixture, not something this PR can reach.

The other 9 entries in the report are flaky (passed on retry), so there's nothing else to triage.

_{Triaged by the Playwright bot - agent run}