Skip to content
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

Closed
dtapuska opened this issue Sep 6, 2018 · 5 comments · Fixed by #8254
Closed

Add ability to query UserActivation state #4008

dtapuska opened this issue Sep 6, 2018 · 5 comments · Fixed by #8254
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: user activation

Comments

@dtapuska
Copy link
Contributor

dtapuska commented Sep 6, 2018

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.

dtapuska added a commit to dtapuska/html that referenced this issue Sep 6, 2018
Describe the interface and augment PostMessage options to contain the
required fields.

Fixes whatwg#4008
@annevk annevk added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest labels Sep 7, 2018
dtapuska added a commit to dtapuska/html that referenced this issue Oct 15, 2019
Describe the interface and augment PostMessage options to contain the
required fields.

Fixes whatwg#4008
dtapuska added a commit to dtapuska/html that referenced this issue Nov 7, 2019
Describe the interface and augment PostMessage options to contain the
required fields.

Fixes whatwg#4008
dtapuska added a commit to dtapuska/html that referenced this issue Dec 12, 2019
Describe the interface and augment PostMessage options to contain the
required fields.

Fixes whatwg#4008
dtapuska added a commit to dtapuska/html that referenced this issue Dec 12, 2019
Describe the interface and augment PostMessage options to contain the
required fields.

Fixes whatwg#4008
@annevk
Copy link
Member

annevk commented Jun 9, 2020

See #4009.

@domenic
Copy link
Member

domenic commented Dec 14, 2021

Note that this is shipping in Chrome. Agenda+ to discuss if any other browsers are interested.

Personally I feel like navigator.userActivation is an easy win. The PostMessageOptions extension is less obviously clear in its utility.

@domenic domenic added the agenda+ To be discussed at a triage meeting label Dec 14, 2021
@domenic
Copy link
Member

domenic commented Dec 14, 2021

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 navigator.userActivation portion, but that's encouraging...

@andreubotella
Copy link
Member

Note that since structuredClone() does nothing with user activation, and #3414 renamed the PostMessageOptions dictionary to StructuredCloneOptions, in https://chromium-review.googlesource.com/c/chromium/src/+/3245334 we decided to bring back the old dictionary name to keep the difference. See dtapuska/useractivation#15.

@annevk
Copy link
Member

annevk commented Dec 15, 2021

I'm a bit surprised to hear something shipped here without the PR being finalized. I had gotten the impression it was abandon-ware.

@past past removed the agenda+ To be discussed at a triage meeting label Feb 3, 2022
mustaqahmed added a commit to mustaqahmed/html that referenced this issue Sep 2, 2022
domenic pushed a commit that referenced this issue Sep 14, 2022
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: user activation
Development

Successfully merging a pull request may close this issue.

5 participants