test(credentials): httpCredentials should not override page's Authorization header

[Yury Semikhatsky (yury-s)]

The issue was fixed in https://github.com/microsoft/playwright-browsers/pull/2487

Closes: #42291

[github-actions]

Test results for "MCP"

1 failed
❌ [chrome] › mcp/config.spec.ts:203 › chromiumSandbox › --sandbox enables the sandbox @mcp-ubuntu-latest-chrome

6325 passed, 944 skipped

---

Merge workflow run.

[github-actions]

Test results for "tests 1"

Warning

The triggering workflow run ended with status cancelled. Results below may be incomplete — blob reports from cancelled or timed-out shards are missing, so passing/failing counts do not reflect the full test suite.

18 flaky

⚠️ [chromium-library] › library/global-fetch.spec.ts:293 › should return security details from response `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/har.spec.ts:639 › should have security details `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/tracing.spec.ts:493 › should produce screencast frames fit `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/video.spec.ts:664 › screencast › should capture full viewport `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/video.spec.ts:699 › screencast › should capture full viewport on hidpi `@chromium-ubuntu-22.04-arm-node20`
⚠️ [chromium-library] › library/global-fetch.spec.ts:293 › should return security details from response `@realtime-time-library-chromium-linux`
⚠️ [chromium-library] › library/har.spec.ts:639 › should have security details `@realtime-time-library-chromium-linux`
⚠️ [chromium-library] › library/global-fetch.spec.ts:293 › should return security details from response `@chromium-ubuntu-22.04-node24`
⚠️ [chromium-library] › library/har.spec.ts:639 › should have security details `@chromium-ubuntu-22.04-node24`
⚠️ [chromium-library] › library/video.spec.ts:356 › screencast › should work for popups `@chromium-ubuntu-22.04-node24`
⚠️ [chromium-library] › library/video.spec.ts:736 › screencast › should work with video+trace `@chromium-ubuntu-22.04-node24`
⚠️ [chromium-library] › library/global-fetch.spec.ts:293 › should return security details from response `@chromium-ubuntu-22.04-node22`
⚠️ [chromium-library] › library/har.spec.ts:639 › should have security details `@chromium-ubuntu-22.04-node22`
⚠️ [chromium-library] › library/trace-viewer-scrub.spec.ts:177 › should drag scrubber to select action `@chromium-ubuntu-22.04-node22`
⚠️ [firefox-library] › library/global-fetch.spec.ts:293 › should return security details from response `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-library] › library/har.spec.ts:639 › should have security details `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-page] › page/page-emulate-media.spec.ts:144 › should keep reduced motion and color emulation after reload `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-page] › page/page-set-input-files.spec.ts:38 › should upload a folder `@firefox-ubuntu-22.04-node20`

33496 passed, 719 skipped

---

Merge workflow run.

[github-actions]

🟢 CI is clear — the one failure is a pre-existing, PR-independent break

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

This PR only adds one test to tests/library/browsercontext-credentials.spec.ts. The sole reported failure is an MCP sandbox test that has nothing to do with credentials — and it's red on that bot for every recent run, not just this one.

Details

Overall: one reported failure, and it's not caused by this PR. The "tests 1" report has zero failures (its run was cancelled, leaving only flaky/interrupted rows — nothing to triage there).

Pre-existing flake / infra

• [chrome] › mcp/config.spec.ts:203 › chromiumSandbox › --sandbox enables the sandbox@mcp-ubuntu-latest-chrome — pre-existing, environment-specific break. In the test-results DB this test has failed 27 of 27 runs on mcp-ubuntu-latest-chrome, across unrelated SHAs and PRs (e.g. push 51023b4, PR fix(chromium): stop disabling BoundaryEventDispatchTracksNodeRemoval #42294) — it was already red before this branch existed. It passes on the other MCP bots, so this is the Linux chrome+--sandbox CI environment, not a flake in the usual sense. This PR touches only browsercontext-credentials.spec.ts, which doesn't exercise the MCP sandbox path.

  Run history on mcp-ubuntu-latest-chrome (oldest → newest): 🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥

• The 18 flaky entries in "tests 1" (security-details, screencast/video, trace-viewer) all passed on retry and are unrelated to credentials.

_{Triaged by the Playwright bot - agent run}