- From: Shih-Chiang Chien via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Apr 2016 08:00:42 +0000
- To: public-secondscreen@w3.org
> But as I understand, one would not need to trigger any action to enter 'connected' state, it's up to the UA. What action did you have in mind? Here is the behavior I have in mind after reading the draft updated yesterday. If UA is still retrying the connection establishment, staying in `connecting` state on both controller and receiver is reasonable. If UA stops retrying connection establishment, this PresentationConnection should enter 'closed' state on both controller and receiver. On controller side, a statechange (from `connecting` to `closed`) event should be fired afterward so that controlling page can trigger connection resumption either automatically or by user action. On receiver side, presentation controllers promise should not be resolved and this PresentationConnection should not be added into PresentationConnectionList. Presented Content will have no knowledge about this closed connection because web page cannot get the reference via any API or event, so it'll looks like that UA is still awaiting the incoming connection. Maybe we can add more detail in step 5, like: ``` If connection completes successfully, Set the presentation connection state of S to connected. Otherwise, set the presentation connection state of S to closed and abort all remaining steps. ``` -- GitHub Notification of comment by schien Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/283#issuecomment-213311818 using your GitHub account
Received on Friday, 22 April 2016 08:00:44 UTC