Monday, 29 February 2016
- RE: Respond to poll on May 2016 F2F dates and location - DL 2016-03-10
- Re: Respond to poll on May 2016 F2F dates and location - DL 2016-03-10
Thursday, 25 February 2016
Tuesday, 23 February 2016
Saturday, 20 February 2016
- [remote-playback] new commits pushed by avayvod
- [remote-playback] new commits pushed by avayvod
- [remote-playback] new commits pushed by avayvod
Wednesday, 17 February 2016
- Re: [presentation-api] [meta] Presentation API Testing
- Re: [presentation-api] [meta] Presentation API Testing
- [presentation-api] new commits pushed by anssiko
Monday, 15 February 2016
- Re: [presentation-api] [meta] Presentation API Testing
- Re: [presentation-api] Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes
- Re: [presentation-api] [meta] Presentation API Testing
- Re: [presentation-api] Split interface Presentation IDL into partials
- [presentation-api] new commits pushed by anssiko
- Closed: [presentation-api] Presentation API IDL Tests for Presentation Interface
- [presentation-api] Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes
- Re: [presentation-api] Split interface Presentation IDL into partials
- [presentation-api] Pull Request: Split interface Presentation IDL into partials
Friday, 12 February 2016
- [presentation-api] [meta] Presentation API Testing
- Closed: [presentation-api] [meta] CfC to publish a new Working Draft
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
- [presentation-api] new commits pushed by anssiko
Thursday, 11 February 2016
- [presentation-api] travis-cl complains about obsolete nvm version
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
- Closed: [presentation-api] [meta] CfC to publish a new Working Draft
- Closed: [presentation-api] Define reconnection for cross-page navigation on presenting user agent
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Clarifies when and how presentations are terminated
- Re: [presentation-api] Clarifies when and how presentations are terminated
- Re: [presentation-api] Clarifies when and how presentations are terminated
- Re: [presentation-api] Clarifies when and how presentations are terminated
- Re: [presentation-api] Editorial changes to termination conditions
- Re: [presentation-api] Clarifies when and how presentations are terminated
- [presentation-api] Pull Request: Editorial changes to termination conditions
- Re: [presentation-api] Clarifies when and how presentations are terminated
Wednesday, 10 February 2016
- [presentation-api] Pull Request: Clarifies when and how presentations are unloaded
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Closed: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
Tuesday, 9 February 2016
- Closed: [presentation-api] Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection?
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Do not trigger "connectionavailable" on reconnect for same presentation
- [presentation-api] Pull Request: Do not trigger "connectionavailable" on reconnect for same presentation
- F2F meeting in May 2016? - please respond by 16 Feb
- Closed: [presentation-api] Specify whether properties of the Presentation are left undefined
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Clarifies handling of Presentation attributes.
Monday, 8 February 2016
- Closed: [presentation-api] Availability URLs versus Presentation URLs
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Closed: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Re: [presentation-api] Presentation API IDL Tests for Presentation Interface
- Re: [presentation-api] Specify whether properties of the Presentation are left undefined
- Re: Progress & issue labeling on GitHub
- Re: [presentation-api] Assess interoperability of Presentation API implementations
Sunday, 7 February 2016
Friday, 5 February 2016
- Re: [presentation-api] Availability URLs versus Presentation URLs
- Progress & issue labeling on GitHub
- Re: [presentation-api] Describe the use cases for terminate vs close
- Re: [presentation-api] Is a new Permission type required for presentation display availability?
- Re: [presentation-api] Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection?
- Re: [presentation-api] Specify whether properties of the Presentation are left undefined
- Re: [presentation-api] Would a "closing" connection state be of any use?
- Closed: [presentation-api] Would a "closing" connection state be of any use?
- Closed: [presentation-api] Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect'
- Re: [presentation-api] Drop use of passive form for event names (issue #256)
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] new commits pushed by anssiko
- Re: [presentation-api] Updates to SoTD to invite wide review of the document
- [presentation-api] Pull Request: Updates to SoTD to invite wide review of the document
- [presentation-api] Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection?
- [presentation-api] Pull Request: Drop use of passive form for event names (issue #256)
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
Thursday, 4 February 2016
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
- Re: [remote-playback] Reconnecting media elements to the playback
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
- [presentation-api] new commits pushed by mfoltzgoogle
- Closed: [presentation-api] Security and privacy considerations
- Re: [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] Need algorithm for establishing a presentation connection when the previous connection(s) were closed
- Closed: [presentation-api] Define a "set of presentations" for the receiving context?
- Closed: [presentation-api] conflict description for uniquely identifying a presentation session
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Split "set of presentations" into controlling/receiving sets
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- Re: [presentation-api] [meta] CfC to publish a new Working Draft
- [presentation-api] Pull Request: Complete Security and Privacy section
Wednesday, 3 February 2016
- Closed: [presentation-api] Think more about privacy implications in multi-user scenarios
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- Closed: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [remote-playback] Reconnecting media elements to the playback
- Re: [remote-playback] Fix markup for promise<boolean>
- [remote-playback] new commits pushed by mounirlamouri
- [remote-playback] Pull Request: Fix markup for promise<boolean>
Tuesday, 2 February 2016
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- Re: [presentation-api] Define reconnection for cross-page navigation on presenting user agent
- Re: [presentation-api] Split "set of presentations" into controlling/receiving sets
- Re: [presentation-api] Would a "closing" connection state be of any use?
- [presentation-api] Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect'
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- Re: [presentation-api] Is a new Permission type required for presentation display availability?
- Re: [presentation-api] Security and privacy considerations
- [presentation-api] Is a new Permission type required for presentation display availability?
- Re: [presentation-api] Split "set of presentations" into controlling/receiving sets
Monday, 1 February 2016
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- [presentation-api] When is the first presentation connection created in the receiving browsing context?
- [presentation-api] Have the receiving browsing context generate the presentation identifier?
- [presentation-api] Pull Request: Split "set of presentations" into controlling/receiving sets
- [presentation-api] Pull Request: Additional UI guidelines for user agents
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time
- Re: [presentation-api] Would a "closing" connection state be of any use?
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] new commits pushed by mfoltzgoogle
- Closed: [presentation-api] binaryType attribute's default value and get/set behaviour needs to be specified
- Re: [presentation-api] Fix #211: Define binaryType default value and get/set behaviour
- Closed: [presentation-api] Presentations from within nested browsing contexts
- Re: [presentation-api] Handling of nested browsing contexts.
- [presentation-api] Pull Request: Fix #211: Define binaryType default value and get/set behaviour
- Re: [presentation-api] Handling of nested browsing contexts.
- Re: [presentation-api] Implementation guideline: users should have a way to know which origin is being presented at any time