Permissions for dynamically created frames#65
Permissions for dynamically created frames#65TiborUdvari wants to merge 1 commit intometa-quest:mainfrom
Conversation
|
Hi @TiborUdvari! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Some online editors, such as the p5.js web editor, create dynamic iframes that don't match the URL of the parent, as I tried to explain in #64. The permission change in this PR enables the polyfill in these contexts. Here is the related documentation.
I setup a minimal example with the barebones-ar immersive example [here] to validate it working. (https://editor.p5js.org/TiborUdvari/sketches/zW9qJtK7V).
I thought that having the permission in the script injected by the service worker would be enough, but through some trial and error I found this is the minimal permission change to make it work. For future reference, there is also a
match_about_blankpermission that might be needed in some cases, although not mine.Here, it is working in the editor after the changes.