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

Feature policy integration #119

Closed
marcoscaceres opened this issue Oct 15, 2019 · 3 comments · Fixed by #112
Closed

Feature policy integration #119

marcoscaceres opened this issue Oct 15, 2019 · 3 comments · Fixed by #112

Comments

@marcoscaceres
Copy link
Member

In #73, @marcoscaceres wrote:

So what if we added a feature policy to prevent third parties from accessing game pads unless the top-level document explicitly says it's ok? That would mitigate some of the privacy concerns and limit some of the damage.

There was consensus that it would be helpful.

@marcoscaceres
Copy link
Member Author

Data to help us with decision making: https://www.chromestatus.com/metrics/feature/timeline/popularity/3054

@mrmcpowned
Copy link

Just to clarify, would the scenario be something like a webpage that embeds an iframe whose source is an external webpage that uses the Gamepad API?

@marcoscaceres
Copy link
Member Author

@mrmcpowned, yes, correct... in which case the following would be needed by hosting site:

<iframe allow="gamepad" src="https://third-party.com"></iframe>

Or a HTTP header that says https://third-party.com is ok to use gamepad... I think it's something like:

Feature-Policy: gamepad https://third-party.com

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

Successfully merging a pull request may close this issue.

2 participants