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
feat: keyboard.lock()
should use permissions helper
#40369
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
Release Notes Persisted
|
I have automatically backported this PR to "26-x-y", please check out #40458 |
I have automatically backported this PR to "27-x-y", please check out #40459 |
I have automatically backported this PR to "28-x-y", please check out #40460 |
feat: `keyboard.lock()` should use permissions helper
Description of Change
Similar APIs are routed through our permissions helper, and it breaks from our permissions expectations to have this API not be controllable through
ses.setPermissionRequestHandler(handler)
.This change brings it in line with other APIs like the
Pointer Lock API
.Checklist
npm test
passesRelease Notes
Notes: Added
keyboardLock
toses.setPermissionRequestHandler(handler)
.