Mounir Lamouri

I don't think at the moment these concerns are likely to lead to something concrete. The website wouldn't receive mouse events, hover, focus, or blur on the PIP window, thus...

`screen.height` and `screen.width` will give you the screen size. I don't think the Picture-in-Picture API is exposing anything new.

I don't think we can fully abstract planes and meshes concepts to the Web API given that there are supposed to be exposed as part of the real world geometry...

I'm not sure that we should never expose anything of the sort but maybe we can mark the `entityTypes` part of the spec as at risk and link to this...

@Manishearth to clarify, the API as-is, without the `entityTypes` parts, looks good to you modulo any unforeseen issues with headsets?

@thetuvix what would be the ideal behaviour in your opinion? How does Hololens generate the planes? Are they generated from the meshes or are they both generated individually? Is there...

Would it make sense to have an extended constructor for `PresentationRequest` that takes a list of `constraints` that could include these information?

We could add a new `MediaError`, set the property and fire an event and maybe do the same when `play()` is called for consistency. However, there might be side effects...

At the moment, we do not want to expose a permission for autoplay. We might want to tell a website whether yes/no they can autoplay but not allow them to...