Rik Cabanier
Rik Cabanier
> > Video layers don't have an inherent pixel width and height. > > It seems to the author that they do. See my first paragraph about XRLayerInit requiring viewPixelWidth...
@dominiccooney I marked it as "future enhancement". Please let me know if you feel strongly that this needs to be in the initial version of the spec.
> Screenshare is interesting, @cabanier do you think a WebRTC Video can be put through a WebXR layer? Yes, any video element can become the source for a video layer.
A big issue with today's definition of DOM Overlays is that they are drawn on top of the VR scene. Unless we change that, I suspect that they can only...
> This requirement intentionally does NOT apply to UI elements drawn by the UA directly. For example, it would be OK for the UA to provide a visible pointer ray,...
> > There's also the issue that people will want more than one surface which is problematic because of DOM Overlay's use of the full screen API > > DOM...
> Thanks for clarifying. Would it be more accurate to say that an implementation or API can basically choose two out of these three features for DOM content, but not...
> To summarize: It allows us to make interactive in-world panels given they're hosted by the same domain, but also import content in a non-interactive way if it's not "secured"...
Correct. cross-domain/top rendering only = DOM Overlay same-origin/arbitrary placement = DOM Layers
> > > Screenshare is interesting, @cabanier do you think a WebRTC Video can be put through a WebXR layer? > > > > > > Yes, any video element...