Repository navigation
docs(input): document Caps Lock state limitation - #44209
Conversation
Test results for "MCP"3 failed 5237 passed, 633 skipped Merge workflow run. |
🟢 These three failures predate this PRHi, I'm the Playwright bot. I checked the MCP failures; none were caused by this documentation change. Details and evidenceChecked MCP run 44351654549 at The diff adds only a Caps Lock note to Pre-existing flake / infra All three failures are in
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 |
Test results for "tests 1"2 failed 1 flaky23641 passed, 716 skipped Merge workflow run. |
🟢 Both JUnit failures predate this PRHi, I'm the Playwright bot. I checked the Details and evidenceChecked run 44351654363 at 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 All four failures are at line 374: expected The small correction is to expect 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 |
Document that pressing
CapsLocksends 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