feat(screencast): style action decorations, keep cursor visible

[Pavel Feldman (pavelfeldman)]

Summary

• showActions({ style: { point, highlight, title } }) takes CSS declarations per decoration; point marker and target highlight are now opt-in
• deprecate fontSize in favor of style.title
• cursor stays at the last action point, survives navigations and travels along a slightly curved, eased path
• macOS-style cursor
• --cursor for video-start, --point-style/--highlight-style/--title-style for video-show-actions

[github-actions]

Test results for "tests 1"

2 failed
❌ [installation tests] › playwright-cdn.spec.ts:43 › playwright cdn failover should work (https://cdn.playwright.dev/dbazure/download/playwright) @package-installations-macos-latest
❌ [installation tests] › playwright-cdn.spec.ts:43 › playwright cdn failover should work (https://playwright.download.prss.microsoft.com/dbazure/download/playwright) @package-installations-macos-latest

7 flaky

⚠️ [chromium-library] › library/video.spec.ts:725 › screencast › should capture full viewport on hidpi `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/chromium/chromium.spec.ts:436 › should produce network events, routing, and annotations for Service Worker (advanced) `@chromium-ubuntu-22.04-node24`
⚠️ [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-library] › library/browsercontext-reuse.spec.ts:200 › reuse connect › should not cache resources `@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`
⚠️ [firefox-page] › page/page-goto.spec.ts:90 › should work with Cross-Origin-Opener-Policy `@firefox-ubuntu-22.04-node20`

51979 passed, 1247 skipped

---

Merge workflow run.

[github-actions]

🟢 Both failures are a known CDN flake — the PR is clear

Hi, I'm the Playwright bot and I triaged the red CI here.

The two failures are installation tests › playwright-cdn.spec.ts:43 › playwright cdn failover should work on package-installations-macos-latest. The same pair fails on this PR's own base sha 6391967, on main pushes, and on eight unrelated PRs — so it's failing without your changes in the tree.

Details

Overall: nothing in this PR reaches browser downloading. The diff is screencast action decorations — packages/injected/src/highlight.{ts,css}, injectedScript.ts, server/screencast.ts, tools/backend/video.ts, protocol/types, and tests/library/screencast-actions.spec.ts. The installation tests exercise npx playwright install against CDN hosts, which none of that touches.

Pre-existing flake / infra

• [installation tests] › playwright-cdn.spec.ts:43 › playwright cdn failover should work (https://cdn.playwright.dev/dbazure/download/playwright) and the https://playwright.download.prss.microsoft.com/… variant — they always fail as a pair. Across the aggregated CI results each failed 18 of 946 runs (2%) and passed the other 928, on 16 distinct shas: this PR's base sha 6391967, main pushes 8bb2c09/24b6932/bf9d04f, and PRs feat(webkit): roll to r2365 #42762, devops(bidi): publish BiDi reports to a git branch instead of Azure #42760, feat(chromium): roll to r1246 #42757, feat(video): allow recording video at a custom fps #42752, feat(webkit): roll to r2364 #42748, feat(webkit): roll to r2363 #42737, feat(webkit): roll to r2362 #42736, fix(reporter): do not hang perfetto writes after a stream error #42715, fix(trace-viewer): reject unsafe snapshot tag names #42712. It spreads across all three installation bots (ubuntu, windows, macos), which is the shape of a CDN/network hiccup rather than anything in the tree. The sibling case (https://cdn.playwright.dev) — same file, no /dbazure failover hop — is 946/946 green, so the flake lives in the failover path itself.

No re-run needed for correctness; a retry should go green.

_{Triaged by the Playwright bot - agent run}

[github-actions]

Test results for "MCP"

1 failed
❌ [firefox] › mcp/idle-timeout.spec.ts:19 › closes the browser after the idle timeout and relaunches it on the next call @mcp-windows-latest-firefox

8602 passed, 1446 skipped

---

Merge workflow run.

[github-actions]

🟢 All three failures are known flakes — the PR is clear

Hi, I'm the Playwright bot and I triaged the red CI here.

The MCP failure is mcp/idle-timeout.spec.ts:19 on mcp-windows-latest-firefox, which fails with the identical error on unrelated PRs #42760 and #42718. The two playwright-cdn.spec.ts:43 failures are the long-running CDN failover flake. Nothing in this PR reaches either code path.

Details

Overall: the diff is screencast action decorations — packages/injected/src/highlight.{ts,css}, injectedScript.ts, server/screencast.ts, the browser_start_video / browser_video_show_actions params in tools/backend/video.ts and tools/cli-daemon/commands.ts, plus protocol/types. The MCP backend change in tools/backend/context.ts is confined to startVideoRecording, which calls screencast.showActions({ cursor }) after the screencast starts. Browser launch and the idle-timeout lifecycle are untouched, and the idle-timeout test never starts a video.

Pre-existing flake / infra

• [firefox] › mcp/idle-timeout.spec.ts:19 › closes the browser after the idle timeout and relaunches it on the next call @mcp-windows-latest-firefox — across the aggregated CI results this test ran 1474 times over 115 shas and failed 3, all three on this one bot (3 of 109 runs there, 3%): this PR's sha b26a1c7, plus devops(bidi): publish BiDi reports to a git branch instead of Azure #42760 (c78538b) and Fix spelling of restoring in credentials docs #42718 (d979f02) two days ago. The error is byte-for-byte the same in all three — the relaunch navigation loses the race with the idle close:

  Error: browserBackend.callTool: Target page, context or browser has been closed
  Call log:
    - navigating to "http://localhost:8907/hello-world", waiting until "domcontentloaded"
  

  Firefox on Windows is the slowest launcher in the matrix, so the 500ms --idle-timeout is tightest there. The other five tests in the same file are green across every run in the window.

• [installation tests] › playwright-cdn.spec.ts:43 › playwright cdn failover should work (https://cdn.playwright.dev/dbazure/download/playwright) and the https://playwright.download.prss.microsoft.com/… variant @package-installations-macos-latest — they always fail as a pair, each 18 of 946 runs (2%) across 16 distinct shas, including this PR's base sha 6391967, main pushes, and PRs feat(webkit): roll to r2365 #42762, devops(bidi): publish BiDi reports to a git branch instead of Azure #42760, feat(chromium): roll to r1246 #42757, feat(video): allow recording video at a custom fps #42752, feat(webkit): roll to r2364 #42748, feat(webkit): roll to r2363 #42737, feat(webkit): roll to r2362 #42736, fix(reporter): do not hang perfetto writes after a stream error #42715, fix(trace-viewer): reject unsafe snapshot tag names #42712. The sibling case without the /dbazure failover hop is 946/946 green, so the flake lives in the failover path itself. Browser downloading isn't something this diff touches.

A retry should go green; nothing here needs a code change.

_{Triaged by the Playwright bot - agent run}