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

[presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous

[presentation-api] [meta] Presentation API Testing

[presentation-api] [SameObject] for receiver seems wrong

[presentation-api] Adds steps for initiating presentation from default presentation request.

[presentation-api] Authenticity of screen selection permission is problematic in insecure contexts

[presentation-api] Clarifies inputs to algorithms.

[presentation-api] Clarifies the roles of objects for getting presentation display availability.

[presentation-api] Clarify arguments to getting presentation displays availability information

[presentation-api] Clarify event order when establishing a presentation connection

[presentation-api] Clarify identities of PresentationConnection objects in reconnect() steps

[presentation-api] Clarify the task source for the specification.

[presentation-api] Clarify when a simultaneous call to start() can be rejected.

[presentation-api] Consider checking for security context in the PresentationRequest constructor

[presentation-api] Determine if we need to fire a terminated event in the receiving browsing context(s)

[presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor

[presentation-api] It is unclear what "If there is already an unsettled Promise from a previous call to start for the same controlling browsing context" means"

[presentation-api] Move mixed content check to PresentationRequest ctor.

[presentation-api] new commits pushed by mfoltzgoogle

[presentation-api] Pull Request: A couple of small fixes to the example code

[presentation-api] Pull Request: Adds steps for initiating presentation from default presentation request.

[presentation-api] Pull Request: Clarifies inputs to algorithms.

[presentation-api] Pull Request: Clarifies the roles of objects for getting presentation display availability

[presentation-api] Pull Request: Clarify identities of PresentationConnection objects in reconnect() steps

[presentation-api] Pull Request: Clarify the task source for the specification.

[presentation-api] Pull Request: Clarify when a simultaneous call to start() can be rejected.

[presentation-api] Pull Request: Move mixed content check to PresentationRequest ctor.

[presentation-api] Pull Request: Remove [SameObject] from navigator.presentation.receiver

[presentation-api] Pull Request: Replace DOMString with USVString for PresentationRequest url and id.

[presentation-api] Remove [SameObject] from navigator.presentation.receiver

[presentation-api] Replace DOMString with USVString for PresentationRequest url and id.

[presentation-api] Replace DOMString with USVString for PresentationRequest URLs.

[presentation-api] setConnection in example 5.5 may put UI in an inconsistent state

[presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection

[presentation-api] Well defined environment for nested contexts of the receiving browsing context?

[remote-playback] Add a privacy and security section

[remote-playback] Add a section about browser initiated remote playback

[remote-playback] Clarify availability monitoring

[remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions

[remote-playback] Define what should happen when device gets disconnected while playing

[remote-playback] Evaluate Security and Privacy impacts

[remote-playback] Getting availability and monitoring list of devices algorithms

[remote-playback] Internationalization considerations

[remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional

[remote-playback] Merge steps 5 and 9 for prompt() algorithm

[remote-playback] new commits pushed by anssiko

[remote-playback] new commits pushed by avayvod

[remote-playback] new commits pushed by mounirlamouri

[remote-playback] new commits pushed by tidoust

[remote-playback] prompt() should not be rejected if the state was connected when called

[remote-playback] Pull Request: Add a privacy and security section

[remote-playback] Pull Request: Add a section about browser initiated remote playback

[remote-playback] Pull Request: Clarify availability monitoring

[remote-playback] Pull Request: SOTD updates to note stability and call for wide review (#58)

[remote-playback] SOTD updates to note stability and call for wide review (#58)

[remote-playback] Update status section

[remote-playback] Use [SameObject] for HTMLMediaElement#remote

Closed: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous

Closed: [presentation-api] [SameObject] for receiver seems wrong

Closed: [presentation-api] Clarify arguments to getting presentation displays availability information

Closed: [presentation-api] define the behavior for consecutive |getAvailability|

Closed: [presentation-api] It is unclear what "If there is already an unsettled Promise from a previous call to start for the same controlling browsing context" means"

Closed: [presentation-api] setConnection in example 5.5 may put UI in an inconsistent state

Closed: [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection

Closed: [presentation-api] Use USVString for URLs

Closed: [remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions

Closed: [remote-playback] Evaluate Security and Privacy impacts

Closed: [remote-playback] Getting availability and monitoring list of devices algorithms

Closed: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional

Closed: [remote-playback] prompt() should not be rejected if the state was connected when called

Closed: [remote-playback] Update status section

Closed: [remote-playback] Use [SameObject] for HTMLMediaElement#remote

New Working Draft of Remote Playback API published

Publish a new Candidate Recommendation for Presentation API?

Remote Playback API reviews requested

Second Screen Working Group Revised Charter Approved; Join Second Screen Working Group (Call for Participation)

Last message date: Wednesday, 30 November 2016 20:18:48 UTC