public-secondscreen@w3.org from December 2015 by subject

[presentation-api] Add a "starting" state to PresentationConnection

[presentation-api] Add a PresentationConnection.disconnected state for accidental disconnections

[presentation-api] Adds a new "connecting" state and per-state event handlers.

[presentation-api] Define a "set of presentations" for the receiving context?

[presentation-api] Define behavior when sending a message to a PresentationSession fails

[presentation-api] define the behavior while receiver calls connection.terminate()

[presentation-api] GitHub API failing, which leads to ReSpec failures

[presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time

[presentation-api] Message sending in Example 5 happens too early

[presentation-api] Need algorithm for establishing a presentation connection when the previous connection(s) were closed

[presentation-api] new commits pushed by mfoltzgoogle

[presentation-api] Presentation API IDL Tests for Presentation Interface

[presentation-api] PresentationReceiver: rename getConnection() and getConnections()

[presentation-api] Provide session lifecycle management for presenting page

[presentation-api] Pull Request: Adds a new "connecting" state and per-state event handlers.

[presentation-api] Pull Request: Reorder api

[presentation-api] Pull Request: Sync example 6 with changes in #221

[presentation-api] ReSpec fails to process current editor's draft

[presentation-api] Security and privacy considerations

[presentation-api] Spec should clarify the initial presentation connection state

[presentation-api] Sync example 6 with changes in #221

[presentation-api] Sync example 6 with changes in #221, rename PresentationReceiver.connections to .connectionList

[presentation-api] Think more about privacy implications in multi-user scenarios

[presentation-api] Update PresentationReceiver spec to match the results from the discussions in #201

[presentation-api] Wrong use of "Queue a task" and "in parallel" in algorithms

[remote-playback] How should disableRemotePlayback/hideRemoteControls behave?

Closed: [presentation-api] Add a "starting" state to PresentationConnection

Closed: [presentation-api] Add a PresentationConnection.disconnected state for accidental disconnections

Closed: [presentation-api] Define behavior when sending a message to a PresentationSession fails

Closed: [presentation-api] Message sending in Example 5 happens too early

Closed: [presentation-api] PresentationReceiver: rename getConnection() and getConnections()

Closed: [presentation-api] Provide session lifecycle management for presenting page

Closed: [presentation-api] Spec should clarify the initial presentation connection state

Fwd: PING call - 3 December - informal chairs summary

Fwd: PING teleconference - 3 December 2015 UTC 17

How to make the best of GitHub for W3C specifications

PING teleconference - 3 December 2015 UTC 17

T.V.L. Global, Not Only Logistics, Also Your Reliable Partner in China

Test Facilitator for the Presentation API

Test suite for the Presentation API (was: Test Facilitator for the Presentation API)

Testing related issues on GH

Welcome to the Second Screen Working Group

Last message date: Saturday, 26 December 2015 23:28:28 UTC