- From: Anton Vayvod via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Oct 2015 19:56:09 +0000
- To: public-secondscreen@w3.org
The F2F meeting notes about the issue 19 that led to the current spec: http://www.w3.org/2015/05/19-webscreens-minutes.html#item12 The argument against having an array property was that the prototype can be changed by the web developers. It doesn't apply to Sequence though afaik. The other argument against the proposal was about supporting a simple use case of one connection - then the page wouldn't need an event handler or care about a sequence of the connections. This is why we left getSession() method. @sicking I think the timing doesn't really matter in the Mounir's example - if the connection is already initialized, it could be populated by the time the page accesses the sequence but if it's not, then the page will receive an event. I think the question now is about the easiness to support the simple use case - one presentation, one connection. We also need to keep in mind a case when the page wants to designate itself as a presentation, that's what ```Promise<> ready``` property could be used for. But as long as it's a backward compatible change, we could add it later. See issue #32 -- GitHub Notif of comment by avayvod See https://github.com/w3c/presentation-api/issues/201#issuecomment-145979653
Received on Tuesday, 6 October 2015 19:56:11 UTC