public-secondscreen@w3.org from January 2016 by author

Anssi Kostiainen via GitHub

• Re: [presentation-api] [meta] CfC to publish a new Working Draft (Friday, 29 January)
• Re: [presentation-api] [meta] CfC to publish a new Working Draft (Friday, 29 January)
• [presentation-api] [meta] CfC to publish a new Working Draft (Tuesday, 26 January)
• Re: [presentation-api] Add a PresentationConnection.disconnected state for accidental disconnections (Monday, 11 January)
• [presentation-api] Pull Request: Make all enum values lowercase for consistency (Monday, 11 January)

Anton Vayvod via GitHub

• [remote-playback] Allow the user agent to choose which media element source to play remotely (Thursday, 28 January)
• [remote-playback] Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback (Monday, 18 January)
• [remote-playback] Reconnecting media elements to the playback (Friday, 15 January)
• [remote-playback] Allow websites to stop the remote playback (Thursday, 14 January)
• Re: [remote-playback] RemotePlayback.state should have events corresponding to state changes (Thursday, 14 January)
• [remote-playback] Add "connecting" to the RemotePlaybackState enum (Thursday, 14 January)
• [remote-playback] RemotePlayback.state should have events corresponding to state changes (Thursday, 14 January)
• [remote-playback] new commits pushed by avayvod (Thursday, 14 January)

Brian Birtles via GitHub

• [presentation-api] Describe the use cases for terminate vs close (Tuesday, 19 January)

Dominique Hazael-Massieux via GitHub

• Re: [presentation-api] ReSpec fails to process current editor's draft (Tuesday, 5 January)

François Daoust via GitHub

• Re: [presentation-api] Define reconnection for cross-page navigation on presenting user agent (Friday, 29 January)
• Re: [presentation-api] [meta] CfC to publish a new Working Draft (Friday, 29 January)
• Re: [presentation-api] getAvailability procedure is not specified (Thursday, 28 January)
• [presentation-api] Pull Request: Re-inserted the getAvailability procedure (Thursday, 28 January)
• [presentation-api] getAvailability procedure is not specified (Wednesday, 27 January)
• [presentation-api] "Known connection" in reconnect() may be linked to another browsing context (Wednesday, 27 January)
• Re: [presentation-api] Evaluate Presentation API against the Media Accessibility User Requirements spec (Wednesday, 27 January)
• Closed: [presentation-api] Run startSession steps in parallel (Wednesday, 27 January)
• Re: [presentation-api] Run startSession steps in parallel (Wednesday, 27 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Thursday, 21 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Wednesday, 20 January)
• [presentation-api] Pull Request: Added enum and event definitions, <var> for variables, fixed references (Wednesday, 20 January)
• Re: [presentation-api] Updated version of PR #238 (Friday, 15 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Friday, 15 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Friday, 15 January)
• Re: [presentation-api] Updated version of PR #238 (Friday, 15 January)
• [presentation-api] bufferedAmount property on PresentationConnection (Tuesday, 12 January)
• Re: [presentation-api] GitHub API failing, which leads to ReSpec failures (Tuesday, 12 January)
• [presentation-api] Would a "closing" connection state be of any use? (Tuesday, 12 January)
• Re: [presentation-api] GitHub API failing, which leads to ReSpec failures (Tuesday, 12 January)
• [presentation-api] Pull Request: Split the "close" algorithm into "closing" and "close" procedures (Monday, 11 January)
• [presentation-api] Pull Request: Fixed use of "fire an event" and "fire a simple event" in the spec (Thursday, 7 January)
• Re: [presentation-api] Algorithms updated to use "queue a task" only when needed (Tuesday, 5 January)
• [presentation-api] Pull Request: Algorithms updated to use "queue a task" only when needed (Tuesday, 5 January)
• Re: [presentation-api] ReSpec fails to process current editor's draft (Monday, 4 January)

Jer Noble via GitHub

• Re: [remote-playback] Reconnecting media elements to the playback (Tuesday, 19 January)

Mark Foltz via GitHub

• [presentation-api] Pull Request: Handling of nested browsing contexts. (Friday, 29 January)
• Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time (Friday, 29 January)
• Re: [presentation-api] [meta] CfC to publish a new Working Draft (Friday, 29 January)
• Closed: [presentation-api] Define security requirements for messaging channel between secure origins (Friday, 29 January)
• Re: [presentation-api] Define security requirements for messaging channel between secure origins (Friday, 29 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Friday, 29 January)
• [presentation-api] Pull Request: Update security requirements for resolution around mixed content. (Thursday, 28 January)
• Closed: [presentation-api] getAvailability procedure is not specified (Thursday, 28 January)
• Re: [presentation-api] getAvailability procedure is not specified (Thursday, 28 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Thursday, 28 January)
• Re: [presentation-api] Re-inserted the getAvailability procedure (Thursday, 28 January)
• Re: [presentation-api] Define security requirements for messaging channel between secure origins (Wednesday, 27 January)
• Re: [presentation-api] Screen availability mechanism for multiple sessions (Wednesday, 27 January)
• Closed: [presentation-api] Screen availability mechanism for multiple sessions (Wednesday, 27 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 27 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Thursday, 21 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 20 January)
• Re: [presentation-api] Added enum and event definitions, <var> for variables, fixed references (Wednesday, 20 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 19 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 19 January)
• Re: [presentation-api] Updated version of PR #238 (Tuesday, 19 January)
• Re: [presentation-api] Updated version of PR #238 (Thursday, 14 January)
• Re: [presentation-api] Updated version of PR #238 (Wednesday, 13 January)
• Re: [presentation-api] GitHub API failing, which leads to ReSpec failures (Tuesday, 12 January)
• Re: [presentation-api] Updated version of PR #238 (Tuesday, 12 January)
• [presentation-api] Pull Request: Updated version of PR #238 (Tuesday, 12 January)
• Re: [presentation-api] Split the "close" algorithm into "closing" and "close" procedures (Monday, 11 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Monday, 11 January)
• Closed: [presentation-api] Add a PresentationConnection.disconnected state for accidental disconnections (Monday, 11 January)
• Re: [presentation-api] Make all enum values lowercase for consistency (Monday, 11 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Thursday, 7 January)
• Closed: [presentation-api] Wrong use of "Queue a task" and "in parallel" in algorithms (Thursday, 7 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Thursday, 7 January)
• Re: [presentation-api] Fixed use of "fire an event" and "fire a simple event" in the spec (Thursday, 7 January)
• Re: [presentation-api] Wrong use of "Queue a task" and "in parallel" in algorithms (Wednesday, 6 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 6 January)
• [presentation-api] Pull Request: Manual merge of PR #234 (Wednesday, 6 January)
• Closed: [presentation-api] ReSpec fails to process current editor's draft (Tuesday, 5 January)
• Re: [presentation-api] ReSpec fails to process current editor's draft (Tuesday, 5 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 5 January)
• Closed: [presentation-api] define the behavior while receiver calls connection.terminate() (Tuesday, 5 January)
• Re: [presentation-api] define the behavior while receiver calls connection.terminate() (Tuesday, 5 January)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 5 January)
• Re: [presentation-api] Algorithms updated to use "queue a task" only when needed (Tuesday, 5 January)
• [presentation-api] Pull Request: Defines behavior for terminate() in controlling and receiving contexts (Monday, 4 January)

Mounir Lamouri via GitHub

• Re: [remote-playback] Add "connecting" to the RemotePlaybackState enum (Wednesday, 27 January)
• Re: [remote-playback] Add "connecting" to the RemotePlaybackState enum (Tuesday, 26 January)
• Re: [remote-playback] Allow websites to stop the remote playback (Monday, 18 January)
• Re: [remote-playback] Add "connecting" to the RemotePlaybackState enum (Monday, 18 January)
• Re: [remote-playback] RemotePlayback.state should have events corresponding to state changes (Monday, 18 January)
• Re: [remote-playback] RemotePlayback.state should have events corresponding to state changes (Monday, 18 January)
• Re: [remote-playback] Reconnecting media elements to the playback (Monday, 18 January)
• Re: [remote-playback] Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback (Monday, 18 January)
• Re: [presentation-api] ReSpec fails to process current editor's draft (Monday, 4 January)

Philip Jägenstedt via GitHub

• Re: [remote-playback] Add "connecting" to the RemotePlaybackState enum (Thursday, 28 January)
• Re: [remote-playback] Add "connecting" to the RemotePlaybackState enum (Tuesday, 26 January)
• Re: [remote-playback] Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback (Tuesday, 26 January)

Tomoyuki Shimizu via GitHub

• Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale (Monday, 25 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Friday, 22 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Thursday, 21 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Wednesday, 20 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Monday, 18 January)
• Re: [presentation-api] Would a "closing" connection state be of any use? (Friday, 15 January)

Last message date: Friday, 29 January 2016 20:40:56 UTC