-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add ability to query UserActivation state #4008
Comments
Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008
Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008
Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008
Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008
Describe the interface and augment PostMessage options to contain the required fields. Fixes whatwg#4008
See #4009. |
Note that this is shipping in Chrome. Agenda+ to discuss if any other browsers are interested. Personally I feel like |
Oh, it seems like other browsers are indeed somewhat interested, per #4009 (comment) . /cc @smaug---- and @whsieh. It's not clear to me whether that was for the full API or just the |
Note that since |
I'm a bit surprised to hear something shipped here without the PR being finalized. I had gotten the impression it was abandon-ware. |
This allows querying both sticky and transient user activation state. Fixes #4008. Closes #4009 by superseding it. See #1983 (which remains open) and https://github.com/dtapuska/useractivation for another related API proposal, for sending user activation state along with message events. Co-authored-by: Dave Tapuska <dtapuska@chromium.org>
Proposal: https://github.com/dtapuska/useractivation
Add an API to query the user activation state and to take a snapshot of it at postMessage time.
The text was updated successfully, but these errors were encountered: