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> has been blocked because of a Feature Policy applied to the current document #3206

Closed
maciejjankowski opened this Issue Feb 2, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@maciejjankowski
Copy link
Contributor

maciejjankowski commented Feb 2, 2018

I get an error when trying to run code which uses MIDI access
Seems like Chrome has recently updated cross-origin frame policies.

See:
https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-permissions-in-cross-origin-iframes

@remy

This comment has been minimized.

Copy link
Member

remy commented Feb 2, 2018

@maciejjankowski

This comment has been minimized.

Copy link
Contributor Author

maciejjankowski commented Feb 2, 2018

I would like to fix it. I need to find out where is the code which creates the runner iframe and add some attributes to it.

@remy

This comment has been minimized.

Copy link
Member

remy commented Feb 2, 2018

The extra trick is that v4 is currently in maintenance and I'm working on v5.

That said, if you think it's just an iframe sandbox prop change, I'll see what it is, and I'll add it to the v5 branch so it's reflected in the new version when it goes live.

I'll see if I can point you in the right direction re: iframe runner…

@remy

This comment has been minimized.

Copy link
Member

remy commented Feb 2, 2018

Pretty sure it's this: https://github.com/jsbin/jsbin/blob/master/public/js/runner/sandbox.js#L27

I think the directions for local running still works, but I can't promise anything (hence the refactor to v5!).

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