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

Clarify how requestPointerLock relies on user activation #67

Closed
marcoscaceres opened this issue Oct 19, 2020 · 4 comments
Closed

Clarify how requestPointerLock relies on user activation #67

marcoscaceres opened this issue Oct 19, 2020 · 4 comments
Assignees
@mustaqahmed

Comments

@marcoscaceres
Copy link
Member

Link to "activation triggering input event" is broken. Not sure what it should link to.
@mustaqahmed
Copy link
Member

This should just point to the definition in HTML spec. That definition needs to be fixed but the PointerLock spec shouldn't worry about the details.

@marcoscaceres
Copy link
Member Author

Right, so, I guess the question is, does it use transient or sticky activation? and will it consume the activation?

@mustaqahmed
Copy link
Member

Yes, this needs to be clarified. The "engagement gesture" idea essentially makes requestPointerLock() a Transient activation-gated API. I will work on a PR next week.

@mustaqahmed mustaqahmed self-assigned this Oct 20, 2020
@mustaqahmed mustaqahmed changed the title "activation triggering input event" no longer a thing Clarify how requestPointerLock relies on user activation Oct 20, 2020
@mustaqahmed mustaqahmed mentioned this issue Jun 15, 2021
Merged
@mustaqahmed mustaqahmed mentioned this issue Oct 26, 2021
Closed
@mustaqahmed
Copy link
Member

This was fixed through #76.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mustaqahmed mustaqahmed

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcoscaceres @mustaqahmed