-
-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Honour multi keypress timeout for NVDA key #17219
Conversation
a6f4eed
to
f4da469
Compare
WalkthroughThe pull request updates the copyright notice in the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
@seanbudd FYI, PR opened against beta. Let me know if it's too late though. |
Link to issue number:
Fix-up of #12049.
Summary of the issue:
When implementing multi keypress timeout in #12049, the timeout for double press of NVDA key (to execute native function) was not honoured.
Description of user facing changes
Multiple key press timeout will now be honoured also for double press of NVDA key.
Description of development approach
Replace the hard-coded value 0.5 with the config value.
Testing strategy:
Manual tests:
Increased the delay to 3000 ms and:
insert
orcapslock
honour the native key function is executedKnown issues with pull request:
Opened against beta since the PR being fixed up is part of this release cycle. But it may be too late to have a test period...
If you do not wish to introduce change at this stage, #12049 can remain in the release though, and I'll rebase on master.
Code Review Checklist:
Summary by CodeRabbit
New Features
Chores