Open thetuvix opened 2 years ago
/facetoface As more of us as vendors enter The Metaverse™, we should warm up previous discussions around showing web content within a WebXR session.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/thetuvix"><img src="https://avatars.githubusercontent.com/u/1209982?v=4" />thetuvix</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>The slides @NellWaliczek's team presented about this back in 2018: <a href="https://www.w3.org/2018/10/iwwg-tpac-slides/2d.pdf">https://www.w3.org/2018/10/iwwg-tpac-slides/2d.pdf</a></p> <p>Some specific questions here:</p> <ul> <li>Any progress on making DOM to Texture safe?</li> <li>Could WebXR DOM Layers work here?</li> <li>Do things like <a href="https://developer.chrome.com/docs/privacy-sandbox/fenced-frame/">fenced frames</a> help?</li> </ul> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/AdaRoseCannon"><img src="https://avatars.githubusercontent.com/u/4225330?v=4" />AdaRoseCannon</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>I know it's a technical and security nightmare but it would be very fun if an iframe web site could start it's own session and the two sessions get smashed together.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/RafaelCintron"><img src="https://avatars.githubusercontent.com/u/8486520?v=4" />RafaelCintron</a> commented <strong> 2 years ago</strong> </div> <div class="markdown-body"> <p>In my view, there are two main ways to solve this problem. </p> <ol> <li> <p><strong>IFrame Textures</strong>. Developers use the <a href="https://www.khronos.org/registry/webgl/extensions/proposals/WEBGL_texture_source_iframe/">WEBGL_texture_source_iframe</a> or similar extension to draw an iframe into a WebGL texture and subsequently use the texture in their WebXR scene. </p> <ul> <li>(Pro) Web developers have the freedom to draw the iframe content in the world however they wish: on a sphere, quad, piece of cloth fluttering in the wind, whatever.</li> <li>(Con) All resources loaded by the iframe must have restrictions discussed in the <a href="https://www.khronos.org/registry/webgl/specs/latest/1.0/#4.2">Origin Restrictions</a> section of the WebGL spec. If elements such as image, video and others are required to have these restrictions today, iframes containing them must also have the same restriction. This drawback was one reason the WebGL_texture_source_iframe extension was not broadly adopted.</li> </ul> </li> <li> <p><strong>DOM Layers</strong>. In this approach, WebXR developers use the WebXR layers API to add a new kind of layer that is navigated to an iframe. </p> <ul> <li>(Good) Since the web contents are drawn by the browser itself and can never be read by a WebGL shader, no origin restrictions are necessary.</li> <li>(Bad) Developers will be limited by the draw order of the DOM layer with respect to other layers. Might be tricky to draw things in front or behind iframe layers. </li> </ul> </li> </ol> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>
/facetoface As more of us as vendors enter The Metaverse™, we should warm up previous discussions around showing