There's an open question of how to give users proper notification and control of 1-UA presentations.  Currently we use a specialized browser window to allow users to see presentations on secondary wired screens.  However other 1-UA presentations to other devices are hidden from the user.

Using this approach for other 1-UA presentations has the following advantages:

- Gives user visibility into what is being presented, even if the user walks away from the screen that is showing it.
- Allows the user to see the URL and security indicators for the presentation (recommended by spec).
- Gives the user another way to close the presentation, other than the Cast dialog.

Things to think through:
- What happens when the user resizes the window?
- If the presentation ends or the stream is interrupted, do we just kill the window or show a message?

 

There's an open question of how to give users proper notification and control of 1-UA presentations.  Currently we use a specialized browser window to allow users to see presentations on secondary wired screens.  However 1-UA presentations to other devices are hidden from the user.

Rendering a browser window for all 1-UA presentations has the following advantages:

- Gives user visibility into what is being presented, even if the user walks away from the screen that is showing it.
- Allows the user to see the URL and security indicators for the presentation (recommended by spec).
- Gives the user another way to close the presentation, other than the Cast dialog.

Things to think through:
- What happens when the user resizes the window?
- If the presentation ends or the stream is interrupted, do we just kill the window or show a message?