public-secondscreen@w3.org from February 2016 by subject

[presentation-api] [meta] CfC to publish a new Working Draft

[presentation-api] [meta] Presentation API Testing

[presentation-api] Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes

[presentation-api] Assess interoperability of Presentation API implementations

[presentation-api] Availability URLs versus Presentation URLs

[presentation-api] bufferedAmount property on PresentationConnection

[presentation-api] Clarifies when and how presentations are terminated

[presentation-api] Define reconnection for cross-page navigation on presenting user agent

[presentation-api] Describe the use cases for terminate vs close

[presentation-api] Do not trigger "connectionavailable" on reconnect for same presentation

[presentation-api] Drop use of passive form for event names (issue #256)

[presentation-api] Editorial changes to termination conditions

[presentation-api] Fix #211: Define binaryType default value and get/set behaviour

[presentation-api] Handling of nested browsing contexts.

[presentation-api] Have the receiving browsing context generate the presentation identifier?

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

[presentation-api] Is a new Permission type required for presentation display availability?

[presentation-api] new commits pushed by anssiko

[presentation-api] new commits pushed by mfoltzgoogle

[presentation-api] Only allow one PresentationAvailability per PresentationRequest

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

[presentation-api] Pull Request: Additional UI guidelines for user agents

[presentation-api] Pull Request: Clarifies handling of Presentation attributes.

[presentation-api] Pull Request: Clarifies when and how presentations are unloaded

[presentation-api] Pull Request: Complete Security and Privacy section

[presentation-api] Pull Request: Do not trigger "connectionavailable" on reconnect for same presentation

[presentation-api] Pull Request: Drop use of passive form for event names (issue #256)

[presentation-api] Pull Request: Editorial changes to termination conditions

[presentation-api] Pull Request: Fix #211: Define binaryType default value and get/set behaviour

[presentation-api] Pull Request: Split "set of presentations" into controlling/receiving sets

[presentation-api] Pull Request: Split interface Presentation IDL into partials

[presentation-api] Pull Request: Updates to SoTD to invite wide review of the document

[presentation-api] Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect'

[presentation-api] Security and privacy considerations

[presentation-api] Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection?

[presentation-api] Specify whether properties of the Presentation are left undefined

[presentation-api] Split "set of presentations" into controlling/receiving sets

[presentation-api] Split interface Presentation IDL into partials

[presentation-api] travis-cl complains about obsolete nvm version

[presentation-api] Updates to SoTD to invite wide review of the document

[presentation-api] When is the first presentation connection created in the receiving browsing context?

[presentation-api] Would a "closing" connection state be of any use?

[remote-playback] Fix markup for promise<boolean>

[remote-playback] new commits pushed by avayvod

[remote-playback] new commits pushed by mounirlamouri

[remote-playback] Pull Request: Fix markup for promise<boolean>

[remote-playback] Reconnecting media elements to the playback

Closed: [presentation-api] "Known connection" in reconnect() may be linked to another browsing context

Closed: [presentation-api] [meta] CfC to publish a new Working Draft

Closed: [presentation-api] Availability URLs versus Presentation URLs

Closed: [presentation-api] binaryType attribute's default value and get/set behaviour needs to be specified

Closed: [presentation-api] conflict description for uniquely identifying a presentation session

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

Closed: [presentation-api] Define reconnection for cross-page navigation on presenting user agent

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

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

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

Closed: [presentation-api] Presentations from within nested browsing contexts

Closed: [presentation-api] Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect'

Closed: [presentation-api] Security and privacy considerations

Closed: [presentation-api] Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection?

Closed: [presentation-api] Specify whether properties of the Presentation are left undefined

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

Closed: [presentation-api] Would a "closing" connection state be of any use?

F2F meeting in May 2016? - please respond by 16 Feb

Progress & issue labeling on GitHub

Respond to poll on May 2016 F2F dates and location - DL 2016-03-10

Last message date: Monday, 29 February 2016 15:50:03 UTC