- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Apr 2016 20:10:59 +0000
- To: public-secondscreen@w3.org
@tidoust, overall looks good. I traced through the various possibilities and concluded the following: 1. There always at most one presentation controllers promise per receiving browsing context 2. There is always at most one PresentationConnectionList per context that will be used to resolve the promise in #1 3. That singleton list gets a 'connected' event as additional connections are made. Since you'll be out I'll merge in your changes and tweak a few things to make those assumptions clearer, and add a step to populate the PresentationConnectionList. Thanks again! -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/278#issuecomment-212583745 using your GitHub account
Received on Wednesday, 20 April 2016 20:11:00 UTC