- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Apr 2015 21:01:02 +0000
- To: public-secondscreen@w3.org
Reply to @anssiko: > To summarize the proposal (assuming I got it right ;-)): Yes, that is exactly what I had in mind. The only detail is what to do when more than one `<iframe>` has the `allow-default-presentation` attribute and the UA initiates presentation. It could pick arbitrarily or allow the user to choose. > Should we require the same for any startSession() invocation from within iframe? How about joinSession()? For `joinSession()` - no, the intent is that no new presentations can be started, only reconnection to existing presentations, so the risk seems low here. For `startSession()` - my inclination is "no," although it would depend on how the user agent would be able to inform the user about which `<iframe>` was requesting presentation. For example, it would be not ideal to have an invisible `<iframe>` on a domain the user was not aware of be able to request presentation at any time. To mitigate any confusion, we could require that the `<iframe>` meet the conditions of being able to show a popup [1] before it could invoke `startSession()`. > I think that for nested content we should in addition require that the top-level browsing context has explicitly opted in to allow iframes to initiate presentation sessions. Sounds good, after we decide on the attribute vs. allow popups conditions for allowing `startSession()` in `<iframe>`s. [1] https://html.spec.whatwg.org/multipage/browsers.html#allowed-to-show-a-popup -- GitHub Notif of comment by mfoltzgoogle See https://github.com/w3c/presentation-api/issues/79#issuecomment-95335159
Received on Wednesday, 22 April 2015 21:01:03 UTC