Make it explicit that Perform Actions should support resetting key input state with Null Key (\ue000)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
In chapter 11. Elements, section 11.4 Interaction:
The key input state used for input may be cleared mid-way through “typing” by sending the null key, which is U+E000 (NULL).
The effect of the \uE000 PUA codepoint is only mentioned in the context of the "dispatch actions for a string" algorithm in §11.4.3 Element Send Keys. My understanding is that typing this key is expected to reset key input state for Perform Actions with a keyboard input source, but that isn't mentioned in §14.4.2 Keyboard Actions.
Some clarification is due here, as tests such as special_keys.py::test_webdriver_special_key_sends_keydown[NULL-expected15] expects this behavior.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read §14.4.2 Keyboard Actions alongside §11.4.3 Element Send Keys, then inspect special_keys.py::test_webdriver_special_key_sends_keydown[NULL-expected15]. Done means the specification explicitly states how U+E000 resets key input state for Perform Actions with a keyboard input source and remains consistent with the test expectation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100