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.

Sign up for GitHub

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

Jump to bottom

Add the ability to query if a user gesture is active #3739

Closed
dtapuska opened this issue Jun 5, 2018 · 2 comments
Closed

Add the ability to query if a user gesture is active #3739

dtapuska opened this issue Jun 5, 2018 · 2 comments

Comments

@dtapuska
Copy link
Contributor

dtapuska commented Jun 5, 2018

We should add the ability to query whether a user gesture is active or not. UA APIs are gated by this functionality and it is impossible for an application to use the same checks to gate access across frame boundaries.

See:
https://github.com/dtapuska/useractivation
https://discourse.wicg.io/t/usergesture-event/2774
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Jun 5, 2018
@dtapuska
Add an API to query whether the window has seen a user gesture.
28f9b5c 
Add a variable on the window object to query whether the frame has
seen a user activation ever.

https://github.com/dtapuska/useractivation
whatwg/html#3739

BUG=846858

Change-Id: I6ca4c80f4096bfae9ca13b175b46df6b4486a6dd
Merged
chromium-wpt-export-bot pushed a commit to web-platform-tests/wpt that referenced this issue Jun 5, 2018
@dtapuska
Add an API to query whether the window has seen a user gesture.
b1082f3 
Add a variable on the window object to query whether the frame has
seen a user activation ever.

https://github.com/dtapuska/useractivation
whatwg/html#3739

BUG=846858

Change-Id: I6ca4c80f4096bfae9ca13b175b46df6b4486a6dd
@RByers
Copy link

RByers commented Jun 6, 2018

Dave, I forgot I had filed #1983 for what I think shares the same motivation as this issue. But I proposed a different solution which may not address the exact same set of use cases your solution proposes. WDYT, want to just update #1983 for your current proposal and call this a dupe of that? Or is there a meaningful difference worth keeping both?

@dtapuska
Copy link
Contributor Author

Duplicate of #1983

@dtapuska dtapuska mentioned this issue Jul 5, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RByers @dtapuska