- From: R. Richards via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Oct 2020 22:40:38 +0000
- To: public-secondscreen@w3.org
Hey @mfoltzgoogle, Thanks for getting back with me! To address your questions: - Local, secondary monitors fit the use case in the situation I have in place. - The content should be rendered in a new document. The use case I have been using the Presentation API for is this: we have a primary application that starts a presentation. We have a secondary application that is presented, and that is an Angular application that we use to control navigation; it hosts an iframe that shows yet another application which uses SSO authentication. The connection between the primary and secondary applications via the presentation API allows us to switch application context on both sides simultaneously. It all works quite well, accept that we must re-authenticate because the secondary application opens in an incognito window. The goal is to get the authentication steps to a minimum. I hope that is clear, and helps you understand the need. For the other request concerning capturing the presentation device for later reuse; I really like the idea of having a checkbox saying, "always use this device for this site." That would work perfectly for what I am thinking. Excellent idea! I would appreciate hearing about any progress toward making these a reality. Thank you! -- GitHub Notification of comment by rdrrichards Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/477#issuecomment-708698196 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 22:40:40 UTC