- From: Mark Foltz (Google) via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Mar 2020 17:11:18 +0000
- To: public-secondscreen@w3.org
@dlibby I think I understand the use case but let me just ask a couple of clarifying questions: 1. If the user has both a primary display and secondary display, you would want the user to be able to choose either target to display the slides fullscreen from one button/icon (so it would make sense to have a picker with both "This display" and "Secondary monitor"? 2. If the user has only a primary display, can you just use requestFullscreen()? Or is it because you want an entirely separate browser window, and don't want the user to have to click once to open the window then a second time to make it fullscreen? For #1, Chrome currently supports 1-UA mode to target presentations to attached wired displays, but we don't consider the "current" display to be a target. If we did, then presentation would be "available" 100% of the time, which could be unexpected from the user's point of view. In this scenario, if applications want this behavior it would make sense to add an option to the PresentationRequest to include the current display. For #2, it could be possible to propagate user activation from window.open to requestFullscreen, but it feels very risky because you would be giving another origin full control over your desktop with a single click. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/476#issuecomment-594670273 using your GitHub account
Received on Wednesday, 4 March 2020 17:11:20 UTC