- From: Mark Foltz (Google) via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Oct 2020 21:54:17 +0000
- To: public-secondscreen@w3.org
Hi @rdrrichards, yes, this is the right forum for making these requests. Sorry it took a while to get back to you! > Specifically, I would like propose that we be allowed to start a presentation in a window that is not a incognito, or in-private, so we can give the end user a better experience when the application being presented requires something like SSO authentication. This is a use case that we have discussed in Issue #347, that would open a presentation window as a child of the current window (like `window.open()`), which would share cookies browser state with the parent. A couple of things I would like to ask, is whether it's important for your use case that: - The presentation window be shown on remote (wireless) displays as well as local, secondary monitors - The presented content has to be rendered in a new document, or if the presented content could be rendered in a frame/element of the original page. > Another enhancement would be that we be able capture the presentation device that end users chose, and that we can automatically use that same device in future presentation requests, if the device is available. That's an interesting idea. This is something that the browser's user interface could support, for example by clicking a box saying "always use this device for this site." Or were you thinking of having two buttons on your site, one to connect to the previous presentation device, and another to choose a new presentation device? -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/477#issuecomment-708680964 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 October 2020 21:54:19 UTC