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

Limit pointerrawupdate and getCoalescedEvents API to secure origins #277

Closed
NavidZ opened this issue Feb 21, 2019 · 1 comment · Fixed by #318
Closed

Limit pointerrawupdate and getCoalescedEvents API to secure origins #277

NavidZ opened this issue Feb 21, 2019 · 1 comment · Fixed by #318
Assignees
Labels

Comments

@NavidZ
Copy link
Member

NavidZ commented Feb 21, 2019

@thiemonagel FYI
Both of getCoaelscedEvents and pointerrawupdate APIs expose some high frequency input and might expose some fingerprinting possibilities to the app.

Limiting this API to the secured origins makes sure only the intended origin has access to this data and no other malicious party over the network.

@NavidZ NavidZ changed the title Limit pointerrawmove and getCoalescedEvents API to secure origins Limit pointerrawupdate and getCoalescedEvents API to secure origins Apr 17, 2019
@smaug----
Copy link
Contributor

If we want to do this, better to do it sooner than later, before non-secure context web pages start to use the APIs heavily. I could imagine some script libraries use the APIs and then one just uses those also outside secure context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants