feat(locator): introduce locator.visible()

[Pavel Feldman (pavelfeldman)]

Summary

• New locator.visible() shortcut, equivalent to filter({ visible: true }), documented as the recommended alternative to the :visible CSS pseudo-class
• Locator generators render visible=true as the shortcut (visible() / .visible / .Visible per language); parser accepts both the shortcut and the filter form
• Console API parity: playwright.locator(...).visible()

[github-actions]

Test results for "tests 1"

6 flaky

⚠️ [chromium-library] › library/video.spec.ts:736 › screencast › should work with video+trace `@frozen-time-library-chromium-linux`
⚠️ [chromium-library] › library/screencast.spec.ts:267 › start dispose stops recording `@chromium-ubuntu-22.04-node24`
⚠️ [chromium-library] › library/video.spec.ts:495 › screencast › should capture static page in persistent context Radoslav Kirilov (@smoke) `@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`

51284 passed, 1241 skipped

---

Merge workflow run.

[github-actions]

Test results for "MCP"

2 failed
❌ [firefox] › mcp/cli-devtools.spec.ts:138 › request* and response* commands support --filename @mcp-windows-latest-firefox
❌ [firefox] › mcp/cli-devtools.spec.ts:199 › recording-start-stop @mcp-windows-latest-firefox

8303 passed, 1367 skipped

---

Merge workflow run.

[github-actions]

🟢 CI is clear — both MCP failures are pre-existing Firefox flakes

Hi, I'm the Playwright bot and I took a first look at the CI failures. Nothing here points back to this PR: the two failed MCP tests are known Firefox/Windows flakes that also fail on unrelated PRs and pushes, and the "tests 1" report only had flaky retries.

Details

This PR adds locator.visible() — client locator, generators/parser, console API, docs and a few tests. It doesn't touch the MCP CLI devtools request/response or recording code paths, so it has no plausible mechanism to break them.

Pre-existing flake / infra

• [firefox] › mcp/cli-devtools.spec.ts:138 › request* and response* commands support --filename — pre-existing flake on mcp-windows-latest-firefox. Across the results DB it failed 3 of 720 firefox runs (2 rescued on retry) and passed the rest, on SHAs unrelated to this PR — e.g. PR test: roll stable-test-runner to 1.63.0-alpha-2026-08-03 #42091, PR chore: remove experimental component testing #42168, and push runs with no PR. Green on all other browsers (chrome/chromium/msedge/webkit: 0 failures over 700+ runs each).
• [firefox] › mcp/cli-devtools.spec.ts:199 › recording-start-stop — pre-existing flake on the same bot. Failed 1 of 121 firefox runs, and separately on PR feat(reporter): introduce TestStep.subtitle, unify step formatting #42422 (2430d745); 0 failures on every other browser.

Both are Firefox-on-Windows only, in code this PR doesn't modify for that engine.

Flaky (no triage needed)

The "tests 1" report listed 6 flaky (video/screencast, third-party cookies, cross-origin request body) and 0 failures — all passed on retry, unrelated to locators.

_{Triaged by the Playwright bot - agent run}