Re: [presentation-api] Same-screen presentation (#476)

@anssiko - Yes, @tidoust has it correct. I should probably have specified that this is mainly geared toward 1-UA mode. And to clarify the mirroring I was referring to was OS-level mirroring (e.g. you connect to a projector and configure the display to mirror your single laptop screen and show that on the projector).

@mfoltzgoogle - 
For (1), I'll need to circle back to fully understand the use case, but I believe having both "This display" and "Secondary monitor" would potentially be ok. In any case, if there were an option on `PresentationRequest` `start()` , the application could be in control over what experience it provides. Thinking through this, `PresentationRequest` `getAvailability()` would indicate whether there are any secondary displays available. If the promise resolves with `PresentationAvailability.value === false`, (and remains false when monitoring `onchange`) the application could then peform a `start()` request that will allow the current display.

For (2), yes, requiring two clicks is the issue with `requestFullscreen()`. The application could be modified to perform requestFullscreen in the same document, but that would be a significant divergence from the PresentationAPI case where a new document is created and communicates with the original. I hadn't considered chaining user activation, but also am not clear whether this would be a good idea in practice, due to the risk you mentioned. 

-- 
GitHub Notification of comment by dlibby-
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/476#issuecomment-594694337 using your GitHub account

Received on Wednesday, 4 March 2020 17:42:57 UTC