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

Need a consistent set of events that defines user activation #3849

Open
mustaqahmed opened this issue Jul 24, 2018 · 3 comments
Open

Need a consistent set of events that defines user activation #3849

mustaqahmed opened this issue Jul 24, 2018 · 3 comments

Comments

@mustaqahmed
Copy link
Contributor

@mustaqahmed mustaqahmed commented Jul 24, 2018

This is related to #1903, where we are working on a user activation model. Here I am isolating the discussion on "events that should trigger a user activation" because this looks like a parallel work that can go ahead with or without the model question.

Current Activation section mentions (among other things) a list of activation triggering events. Unfortunately the list doesn't represent the reality. A recent catalog of activation-triggering events in Chrome, Edge, Firefox and Safari shows the big inconsistencies we have today, sometimes even between desktop and mobile versions of the same browser.

We need to fix this.

One challenging point is the possibility that the set of events could be API-specific!

@mustaqahmed

This comment has been minimized.

Copy link
Contributor Author

@mustaqahmed mustaqahmed commented Jul 24, 2018

Chromium bug to track this: https://crbug.com/826293

@RByers

This comment has been minimized.

Copy link

@RByers RByers commented Oct 22, 2018

FWIW, I'm convinced by the argument here that in addition to a standardized list of events, we should have some single API to be informed of when frame has been activated (to prevent developers from having to maintain a hard-coded list of events, etc.).

In particular, the use case of starting the background music for a game is a good one - it's reasonable to want to do that as soon as the user has indicated any interaction, without necessarily caring what exact form that interaction comes in (eg. launching a PWA, or pressing a gamepad button which fires no dom events at all).

@RByers

This comment has been minimized.

Copy link

@RByers RByers commented Oct 23, 2018

Sorry, I missed @mustaqahmed's response in the WICG thread on this. Let's discuss this particular issue there in the WICG and come back here with any concrete proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.