Skip to content

docs(input): document Caps Lock state limitation - #44209

Merged
Devin Rousso (dcrousso) merged 1 commit into
mainfrom
fix-44200-44350212425-1
Nov 18, 2026
Merged

Devin Rousso (dcrousso) merged 1 commit into
mainfrom
fix-44200-44350212425-1

Conversation

@microsoft-playwright-automation

@microsoft-playwright-automation microsoft-playwright-automation Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Document that pressing CapsLock sends keyboard events but does not make subsequent lowercase input uppercase. Point users to explicit uppercase input instead; keyboard behavior is unchanged.

Refs #44200

Triaged on Linux by the Playwright bot - agent run

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

3 failed
❌ [chrome] › mcp/crash.spec.ts:31 › crash recovery › reports the navigation error, then resets and logs the crash @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:58 › crash recovery › lists only one tab @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:79 › crash recovery › marks non-current crashed tab in the tab list @mcp-ubuntu-latest-chrome

5237 passed, 633 skipped


Merge workflow run.

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor Author

🟢 These three failures predate this PR

Hi, I'm the Playwright bot. I checked the MCP failures; none were caused by this documentation change.

Details and evidence

Checked MCP run 44351654549 at d032fc083b930d6cc5c9f07e242325cf59e332e9, using its merged report.

The diff adds only a Caps Lock note to class-keyboard.md and the generated declaration comments. It changes no executable code, tests, or crash-recovery behavior.

Pre-existing flake / infra

All three failures are in [chrome], on mcp-ubuntu-latest-chrome:

  • mcp/crash.spec.ts:31 — reports the navigation error, then resets and logs the crash.
  • mcp/crash.spec.ts:58 — lists only one tab.
  • mcp/crash.spec.ts:79 — marks non-current crashed tab in the tab list.

The same three tests failed on the same browser and platform in the earlier MCP report for #44208 and MCP report for #44195, both before this PR opened. This confirms that the failures are pre-existing, not a regression from this PR. It does not establish whether they are intermittent or consistently failing.

Full logs and the test-history database required authentication that was unavailable, so the exact crash-recovery failure cause remains unverified.

Checked the failures on Linux by the Playwright bot - agent run

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "tests 1"

2 failed
❌ [playwright-test] › reporter-junit.spec.ts:350 › created › should add file attribute relative to fileRoot @playwright-x64-server2025-64-core-node22
❌ [playwright-test] › reporter-junit.spec.ts:350 › merged › should add file attribute relative to fileRoot @playwright-x64-server2025-64-core-node22

1 flaky ⚠️ [webkit-library] › library/global-fetch.spec.ts:337 › FE-024 should return security details for certificate with multiple CN attributes `@webkit-playwright-x64-ubuntu24-64-core-node22`

23641 passed, 716 skipped


Merge workflow run.

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor Author

🟢 Both JUnit failures predate this PR

Hi, I'm the Playwright bot. I checked the tests 1 failures; neither was caused by this documentation change.

Details and evidence

Checked run 44351654363 at d032fc083b930d6cc5c9f07e242325cf59e332e9, including its Windows job.

The diff adds only a Caps Lock note to the keyboard documentation and generated declaration comments. It changes no executable code, reporter tests, or shared helpers.

Pre-existing flake / infra

Both created and merged variants of [playwright-test] › reporter-junit.spec.ts:350 › should add file attribute relative to fileRoot also failed in the earlier Windows job on main, at 8124fc39233c4c349b9dbebd4abc4103738eae81.

All four failures are at line 374: expected auth/a.test.js, received auth\a.test.js. The reporter and test are unchanged between that commit and this PR. This is a pre-existing Windows test defect, not evidence of an intermittent flake: classname preserves the platform's path separator, while the file attribute is explicitly converted to forward slashes.

The small correction is to expect path.join('auth', 'a.test.js') for classname; keep the forward-slash expectations for file. No change to this PR is needed for these failures.

The WebKit certificate test passed on retry, so it is not counted as a failure. The MCP failures already have a separate verdict above.

Checked the failures on Linux by the Playwright bot - agent run

@dcrousso
Devin Rousso (dcrousso) marked this pull request as ready for review November 18, 2026 20:45
@dcrousso
Devin Rousso (dcrousso) merged commit e245c3f into main Nov 18, 2026
29 of 31 checks passed
@dcrousso
Devin Rousso (dcrousso) deleted the fix-44200-44350212425-1 branch November 18, 2026 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant