Friday, 29 April 2016
- [presentation-api] define the detailed behavior of disable Presentation API in sandbox
- Re: [presentation-api] [meta] Presentation API Testing
Thursday, 28 April 2016
- [presentation-api] Pull Request: Clarified which UA performs the receiving browsing context step
- Welcome to the Second Screen Working Group
Tuesday, 26 April 2016
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- [presentation-api] Pull Request: Remove redundant paragraph.
- Closed: [presentation-api] clean up description for section 6.7.1
- [presentation-api] new commits pushed by mfoltzgoogle
- [remote-playback] Pull Request: Add an examples section introduction.
- Re: [presentation-api] clean up description for section 6.7.1
- [presentation-api] clean up description for section 6.7.1
Monday, 25 April 2016
- Re: [presentation-api] Is a new Permission type required for presentation display availability?
- Re: [presentation-api] Is a new Permission type required for presentation display availability?
- Re: [presentation-api] Specify the algorithm for generating a presentation identifier
- Closed: [presentation-api] Specify the algorithm for generating a presentation identifier
- Re: [presentation-api] Have the receiving browsing context generate the presentation identifier?
- Closed: [presentation-api] Have the receiving browsing context generate the presentation identifier?
- [presentation-api] new commits pushed by mfoltzgoogle
- F2F registration closes this Friday - please register
Friday, 22 April 2016
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
Thursday, 21 April 2016
- Re: [presentation-api] Specify the algorithm for generating a presentation identifier
- Re: [presentation-api] Have the receiving browsing context generate the presentation identifier?
- [presentation-api] Pull Request: Establishes the algorithm for generating the presentation id.
- Re: [presentation-api] Specify the algorithm for generating a presentation identifier
- Closed: [presentation-api] PresentationReceiver.connectionList doesn't return the same object all the time
- Re: [presentation-api] PresentationReceiver.connectionList doesn't return the same object all the time
- Re: [presentation-api] PresentationConnectionClosedEventInit.message needs to have a default value
- Closed: [presentation-api] PresentationConnectionClosedEventInit.message needs to have a default value
- Closed: [presentation-api] Only allow one PresentationAvailability per PresentationRequest
- Re: [presentation-api] Only allow one PresentationAvailability per PresentationRequest
- Closed: [presentation-api] When is the first presentation connection created in the receiving browsing context?
- Re: [presentation-api] When is the first presentation connection created in the receiving browsing context?
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Address issues #254, #269, #273
- Closed: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Adds spec language around localization
- Re: [remote-playback] Add [CEReactions] annotation to disableRemotePlayback
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- [remote-playback] new commits pushed by avayvod
- [remote-playback] new commits pushed by avayvod
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- Re: [remote-playback] Add [CEReactions] annotation to disableRemotePlayback
- Re: [presentation-api] define error handling if fail to establish presentation connection on receiving UA
- [presentation-api] define error handling if fail to establish presentation connection on receiving UA
Wednesday, 20 April 2016
- [presentation-api] [Streams] Prototype a Streams API compatible PresentationConnection
- Closed: [presentation-api] PresentationSession should have stream interfaces!
- Re: [presentation-api] PresentationSession should have stream interfaces!
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
- [remote-playback] Pull Request: Add [CEReactions] annotation to disableRemotePlayback
- Re: [presentation-api] Evaluate Presentation API against the Media Accessibility User Requirements spec
- Closed: [presentation-api] Evaluate Presentation API against the Media Accessibility User Requirements spec
- Re: [remote-playback] Added an introduction section
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
- [presentation-api] PresentationReceiver.connectionList doesn't return the same object all the time
Tuesday, 19 April 2016
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- Closed: [presentation-api] bufferedAmount property on PresentationConnection
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- [presentation-api] Pull Request: Adds spec language around localization
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
- Re: [remote-playback] Added an introduction section
- [remote-playback] Pull Request: Added an introduction section
- Re: [presentation-api] PresentationSession should have stream interfaces!
- Re: [presentation-api] Have the receiving browsing context generate the presentation identifier?
- [presentation-api] Specify the algorithm for generating a presentation identifier
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
- Re: [presentation-api] [meta] Publish Candidate Recommendation
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
Monday, 18 April 2016
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- Re: [presentation-api] Have the receiving browsing context generate the presentation identifier?
- Re: [presentation-api] bufferedAmount property on PresentationConnection
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] Possibility for a character to be interpreted differently depending on locale
- Re: [presentation-api] PresentationSession should have stream interfaces!
- Re: [presentation-api] Updates to PR #277 that addresses issues #254, #269, #273
Friday, 15 April 2016
- [presentation-api] Pull Request: Updates to PR #277 that addresses issues #254, #269, #273
- Re: F2F registration open (24-25 May, 2016, Mountain View, CA, USA)
Thursday, 14 April 2016
- [presentation-api] Pull Request: Address issues #254, #269, #273
- Closed: [presentation-api] Use NotAllowedError for permission denied instead of AbortError
- Re: [presentation-api] Use NotAllowedError for permission denied instead of AbortError
Wednesday, 13 April 2016
Tuesday, 12 April 2016
- Re: [presentation-api] [meta] Publish Candidate Recommendation
- Re: [presentation-api] Evaluate Presentation API against the Media Accessibility User Requirements spec
Friday, 8 April 2016
Wednesday, 6 April 2016
- Re: [presentation-api] [meta] Publish Candidate Recommendation
- Re: [presentation-api] Presentations without communication channel
- Re: W3C Headlights 2016
- W3C Headlights 2016
Monday, 4 April 2016
- [remote-playback] [meta] Publish First Public Working Draft
- [presentation-api] [meta] Publish Candidate Recommendation