Updates to WebVR - New iFrame Attribute: allow=”vr”
In mid November, Google started to roll out Chrome 62 mobile web browser to various mobile devices. Included in this update were several changes to the WebVR standard. Some of these changes, unfortunately, are having a negative effect on iframe embedded WebVR content such at Matterport WebVR Spaces.
Starting with Chrome 62, WebVR content is now required to include the allow=”vr” attribute in the iframe code in order to launch from a 3rd party domain such as my.matterport.com. With this change, any Matterport Space that is currently embedded within a website or app will need to have its iframe code updated to include the allow=”vr” attribute. Without this attribute, the WebVR content will not be accessible even from supported devices.
We are working to update the default iframe embed code generated for each Matterport Space on Cloud to include this attribute by default, however, this update will not affect Spaces that are currently embedded. Regrettably, the only way to insure proper WebVR support is for users to update the embed codes within their own webpages or apps.
Please note that this issue only affects Spaces that have been embedded into another website or app. If you launch the Matterport Tour directly, you will be able to view the WebVR content on your supported devices without issue.
If you have any questions, please feel free to reply to this post, or contact a member of our Support Team at email@example.com
Product Manager - Matterport VR
Example i-frame Update
<iframe width='853' height='480' src='https://my.matterport.com/show/?m=KGNW8SXcYRG' frameborder='0' allowfullscreen></iframe>
After (difference in bold)
<iframe width='853' height='480' src='https://my.matterport.com/show/?m=KGNW8SXcYRG' frameborder='0' allowfullscreen allow=”vr”></iframe>
Users can access WebVR content if they launch it directly from my.matterport.com/show/?m=xxxxxxxxxxx instead of their own webpage or app.