test: JSHandle.getProperties() returns own properties only

[Dmitry Gozman (dgozman)]

Fixes #42651.

[github-actions]

Test results for "tests 1"

1 failed
❌ [firefox-library] › library/browsercontext-storage-state.spec.ts:453 › should work when service worker is intefering and the origin is not open @firefox-ubuntu-22.04-node20

5 flaky

⚠️ [chromium-library] › library/tracing.spec.ts:533 › should produce screencast frames fit `@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:699 › screencast › should capture full viewport on hidpi `@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`

51730 passed, 1247 skipped

---

Merge workflow run.

[github-actions]

🟢 The one failure is pre-existing — this PR is clear

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

[firefox-library] › library/browsercontext-storage-state.spec.ts:453 › should work when service worker is intefering and the origin is not open is broken on main, not by this PR. It fails on the PR's own base sha ad86e96 (run 35130186999) and on every recent unrelated PR.

Details

This PR only adds a test to tests/page/jshandle-properties.spec.ts and renames a neighbouring one — no product code, and nothing the storage-state/service-worker path imports. The single failure is unrelated on every axis.

Pre-existing flake / infra

• [firefox-library] › library/browsercontext-storage-state.spec.ts:453 › should work when service worker is intefering and the origin is not open — not a flake so much as a persistently broken test on Firefox. In the aggregated CI results it has failed 37 of 38 runs on firefox-ubuntu-22.04-node20 since 2026-09-10, and 19/19, 19/19, 19/19, 18/18 on firefox-macos-15-large, firefox-macos-15-xlarge, tracing-firefox and firefox-windows-latest since 2026-09-14. Failures land on push runs of main (shas ad86e96, 49d290a, 1820528) and on unrelated PRs feat(webkit): roll to r2364 #42748, feat(firefox): roll to r1548 #42747, feat(webkit): roll to r2363 #42737, test: evaluate() with falsy result #42728, feat(coverage): experimental istanbul coverage collection via tracing #42684. The assertion is a cookie leak, not a timeout: the storage state carries an extra fromServiceWorker=yes cookie that Firefox now keeps.

  expect(received).toEqual(expected)
  + Object { "name": "fromServiceWorker", "value": "yes" }
  

The 5 flaky results (tracing/video screencast on Chromium, third-party Partitioned; cookies on Firefox) all passed on retry and touch nothing this PR changes.

_{Triaged by the Playwright bot - agent run}

[github-actions]

Test results for "MCP"

1 failed
❌ [chrome] › mcp/annotate.spec.ts:137 › should abort MCP annotation when last screenshot is removed @mcp-windows-latest-chrome

8576 passed, 1446 skipped

---

Merge workflow run.

[github-actions]

🟢 The single MCP failure is a known flake — this PR is clear

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

[chrome] › mcp/annotate.spec.ts:137 › should abort MCP annotation when last screenshot is removed has been failing the same way on unrelated PRs and on main for weeks. This PR is test-only (tests/page/jshandle-properties.spec.ts), so it can't reach the MCP annotate dashboard.

Details

The PR adds one test to tests/page/jshandle-properties.spec.ts and touches no product code, no shared helper, and nothing under packages/playwright/src/mcp. Both failures across the reports are unrelated on every axis.

Pre-existing flake / infra

• [chrome] › mcp/annotate.spec.ts:137 › should abort MCP annotation when last screenshot is removed @mcp-windows-latest-chrome — a long-running Windows-only flake. In the aggregated CI results it flips verdict on every Windows MCP bot: 2/709 failed on mcp-windows-latest-chrome, 8/694 on mcp-windows-latest-firefox, 2/708 on mcp-windows-latest-msedge, always with the identical assertion:

  expect(locator).toHaveCount(expected) failed
  Locator:  locator('.annotate-sidebar-thumb')
  Expected: 1
  Received: 0 / undefined
  

  Prior hits include push runs of main (11ade07, fa2bfcf, 13dbf10, 03a69df, bee00ad, 4acdb2f) and unrelated PRs feat(firefox): roll to r1548 #42747, fix(chromium): restore automation launch flag #42403, fix(chromium): stop disabling BoundaryEventDispatchTracksNodeRemoval #42294, chore(deps): bump the github-actions group with 7 updates #42132, fix(fetch): do not crash on late EPIPE after refused body #42116 — the oldest of them predates this branch by six weeks.

• [firefox-library] › library/browsercontext-storage-state.spec.ts:453 › should work when service worker is intefering and the origin is not open (from the "tests 1" report) — already triaged above: broken on main, failing 37 of 38 recent runs on firefox-ubuntu-22.04-node20, unchanged here.

The 5 flaky results in "tests 1" (tracing/video screencast on Chromium, third-party Partitioned; cookies on Firefox) all passed on retry and touch nothing this PR changes.

_{Triaged by the Playwright bot - agent run}