Mark Foltz

From https://www.w3.org/2017/11/06-webscreens-minutes.html#x18: ACTION: @mfoltzgoogle to check the spec language is aligned with "presentation started but cannot communicate, then close connection"

At least for the DIAL (and presumably HbbTV 2.0) use cases, closing the connection leaves the controlling page unable to terminate the presentation (which is possible via DIAL). So I...

As discussed in https://github.com/w3c/presentation-api/pull/484, there's no way to accommodate these scenarios without some kind of API change. Since Chrome has no plans to ship presentation receivers that don't have some...

Labeling for possible followup at TPAC.

Two references I've found in the W3C space around what "private browsing mode" means include: [W3C TAG Observations on Private Browsing Modes](https://www.w3.org/2001/tag/doc/private-browsing-modes/) and [Standardizing Privacy-Oriented Standards Deviations, in Web Standards](https://github.com/w3cping/privacy-mode/blob/main/private-browsing.md)...

From TPAC F2F: https://www.w3.org/2019/09/16-webscreens-minutes.html#x04 RESOLVED: Create a pull request for a common prompt along the lines presented and gather feedback on the design from other groups WebXR and WebRTC came...

Possible background material: [W3C Workshop on Permissions and User Consent](https://www.w3.org/Privacy/permissions-ws-2018/report.html)

These are some interesting thoughts, thank you for noting them. Trust of a name-to-key binding in the 1.0 spec happens as part of the mutual authentication handshake outlined in the...

CC @btolsch

For the streaming protocol capabilities, I would have to do some research to find out what the use cases are for `max-pixels-per-second` and `supports-rotation`. In general, if there are properties...