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

Wednesday, 30 November 2016

• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts Mark Foltz via GitHub
• Closed: [remote-playback] Evaluate Security and Privacy impacts Anton Vayvod via GitHub
• Re: [remote-playback] Evaluate Security and Privacy impacts Anton Vayvod via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection Mark Foltz via GitHub
• Re: [remote-playback] Add a privacy and security section Anton Vayvod via GitHub
• [remote-playback] Pull Request: Add a privacy and security section Anton Vayvod via GitHub
• Re: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor Anne van Kesteren via GitHub
• Re: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor Mounir Lamouri via GitHub
• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts Anne van Kesteren via GitHub
• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts Anne van Kesteren via GitHub
• Re: Publish a new Candidate Recommendation for Presentation API? mark a. foltz

Tuesday, 29 November 2016

• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Mark Foltz via GitHub
• [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts Mark Foltz via GitHub
• Closed: [presentation-api] Clarify arguments to getting presentation displays availability information Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. Mounir Lamouri via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection Anne van Kesteren via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection François Daoust via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Anne van Kesteren via GitHub
• Re: [presentation-api] Clarifies inputs to algorithms. François Daoust via GitHub
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. François Daoust via GitHub

Monday, 28 November 2016

• [presentation-api] Pull Request: Clarifies inputs to algorithms. Mark Foltz via GitHub
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. Mark Foltz via GitHub
• [presentation-api] Pull Request: Move mixed content check to PresentationRequest ctor. Mark Foltz via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Mark Foltz via GitHub
• Closed: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous Mark Foltz via GitHub
• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous Mark Foltz via GitHub
• Re: [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" Mark Foltz via GitHub
• 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" Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Closed: [presentation-api] define the behavior for consecutive |getAvailability| Mark Foltz via GitHub
• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Closed: [presentation-api] [SameObject] for receiver seems wrong Mark Foltz via GitHub
• Re: [presentation-api] Remove [SameObject] from navigator.presentation.receiver Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub

Thursday, 24 November 2016

• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. Mark Foltz via GitHub

Wednesday, 23 November 2016

• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Closed: [presentation-api] Use USVString for URLs Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor François Daoust via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Mike West via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Anne van Kesteren via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Anne van Kesteren via GitHub

Tuesday, 22 November 2016

• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. Anne van Kesteren via GitHub
• Re: [presentation-api] Adds steps for initiating presentation from default presentation request. Mark Foltz via GitHub
• Closed: [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. Mark Foltz via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection Mark Foltz via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Mark Foltz via GitHub
• Re: Publish a new Candidate Recommendation for Presentation API? Francois Daoust
• Re: [presentation-api] Clarify identities of PresentationConnection objects in reconnect() steps François Daoust via GitHub
• Re: [presentation-api] Clarify the task source for the specification. François Daoust via GitHub
• Re: [presentation-api] Clarify event order when establishing a presentation connection François Daoust via GitHub
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Anne van Kesteren via GitHub
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. Anne van Kesteren via GitHub
• Publish a new Candidate Recommendation for Presentation API? mark a. foltz
• Re: [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection Mark Foltz via GitHub
• [presentation-api] Pull Request: Clarify identities of PresentationConnection objects in reconnect() steps Mark Foltz via GitHub

Monday, 21 November 2016

• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor Mark Foltz via GitHub
• Re: [presentation-api] Clarify arguments to getting presentation displays availability information Mark Foltz via GitHub
• Re: [presentation-api] Well defined environment for nested contexts of the receiving browsing context? Mark Foltz via GitHub
• Re: [presentation-api] Remove [SameObject] from navigator.presentation.receiver Mark Foltz via GitHub
• [presentation-api] Pull Request: Remove [SameObject] from navigator.presentation.receiver Mark Foltz via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong Mark Foltz via GitHub
• [presentation-api] Determine if we need to fire a terminated event in the receiving browsing context(s) Mark Foltz via GitHub
• Re: [presentation-api] Clarify when a simultaneous call to start() can be rejected. Mark Foltz via GitHub
• [presentation-api] Pull Request: Clarify when a simultaneous call to start() can be rejected. Mark Foltz via GitHub
• Re: [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" Mark Foltz via GitHub
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. Mark Foltz via GitHub
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest url and id. Mark Foltz via GitHub

Saturday, 19 November 2016

• [presentation-api] Pull Request: Replace DOMString with USVString for PresentationRequest url and id. Mark Foltz via GitHub
• Re: [presentation-api] Clarify the task source for the specification. Mark Foltz via GitHub
• [presentation-api] Pull Request: Clarify the task source for the specification. Mark Foltz via GitHub

Friday, 18 November 2016

• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. Mark Foltz via GitHub
• [presentation-api] Pull Request: Clarifies the roles of objects for getting presentation display availability Mark Foltz via GitHub
• Re: [presentation-api] Adds steps for initiating presentation from default presentation request. Mark Foltz via GitHub
• [presentation-api] Pull Request: Adds steps for initiating presentation from default presentation request. Mark Foltz via GitHub

Thursday, 17 November 2016

• Closed: [remote-playback] prompt() should not be rejected if the state was connected when called Mounir Lamouri via GitHub
• Re: [remote-playback] prompt() should not be rejected if the state was connected when called Mounir Lamouri via GitHub

Wednesday, 16 November 2016

• Closed: [presentation-api] setConnection in example 5.5 may put UI in an inconsistent state Mark Foltz via GitHub
• Re: [presentation-api] setConnection in example 5.5 may put UI in an inconsistent state Mark Foltz via GitHub
• [presentation-api] new commits pushed by mfoltzgoogle Mark Foltz via GitHub
• [presentation-api] Pull Request: A couple of small fixes to the example code Mark Foltz via GitHub
• Re: [remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions Mounir Lamouri via GitHub
• Closed: [remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions Mounir Lamouri via GitHub
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Anton Vayvod via GitHub
• Closed: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Anton Vayvod via GitHub
• Closed: [remote-playback] Use [SameObject] for HTMLMediaElement#remote Mounir Lamouri via GitHub
• [remote-playback] new commits pushed by mounirlamouri Mounir Lamouri via GitHub
• [presentation-api] Well defined environment for nested contexts of the receiving browsing context? François Daoust via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong François Daoust via GitHub
• [remote-playback] Use [SameObject] for HTMLMediaElement#remote Philip Jägenstedt via GitHub

Tuesday, 15 November 2016

• Re: [presentation-api] Clarify event order when establishing a presentation connection François Daoust via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong François Daoust via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong Anne van Kesteren via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong François Daoust via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong Anne van Kesteren via GitHub

Monday, 14 November 2016

• Re: [presentation-api] [SameObject] for receiver seems wrong François Daoust via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong Anne van Kesteren via GitHub
• Re: [presentation-api] [SameObject] for receiver seems wrong François Daoust via GitHub

Saturday, 12 November 2016

• Re: [remote-playback] Define what should happen when device gets disconnected while playing Mounir Lamouri via GitHub
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Mounir Lamouri via GitHub
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm Mounir Lamouri via GitHub
• [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection Mark Foltz via GitHub

Friday, 11 November 2016

• Re: [remote-playback] Define what should happen when device gets disconnected while playing Anton Vayvod via GitHub
• Re: [remote-playback] Define what should happen when device gets disconnected while playing Anton Vayvod via GitHub
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Anton Vayvod via GitHub
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm Anton Vayvod via GitHub
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm Mounir Lamouri via GitHub
• Re: [remote-playback] Define what should happen when device gets disconnected while playing Mounir Lamouri via GitHub
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Mounir Lamouri via GitHub

Wednesday, 9 November 2016

• [presentation-api] [SameObject] for receiver seems wrong Anne van Kesteren via GitHub
• Remote Playback API reviews requested Francois Daoust
• [remote-playback] Evaluate Security and Privacy impacts François Daoust via GitHub
• [remote-playback] Internationalization considerations François Daoust via GitHub

Tuesday, 8 November 2016

• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous Mark Foltz via GitHub
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Mark Foltz via GitHub
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm Mark Foltz via GitHub

Monday, 7 November 2016

• Closed: [remote-playback] Update status section François Daoust via GitHub
• Re: [remote-playback] Update status section François Daoust via GitHub
• Re: New Working Draft of Remote Playback API published Kostiainen, Anssi
• New Working Draft of Remote Playback API published Francois Daoust
• [remote-playback] new commits pushed by tidoust François Daoust via GitHub

Saturday, 5 November 2016

• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous Louay Bassbouss via GitHub
• [remote-playback] new commits pushed by avayvod Anton Vayvod via GitHub
• [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional Anton Vayvod via GitHub

Friday, 4 November 2016

• [remote-playback] Merge steps 5 and 9 for prompt() algorithm Anton Vayvod via GitHub
• [remote-playback] new commits pushed by avayvod Anton Vayvod via GitHub

Thursday, 3 November 2016

• Re: [remote-playback] prompt() should not be rejected if the state was connected when called Anton Vayvod via GitHub
• Re: [presentation-api] [meta] Presentation API Testing Mark Foltz via GitHub
• [remote-playback] prompt() should not be rejected if the state was connected when called Mounir Lamouri via GitHub
• Re: [remote-playback] Add a section about browser initiated remote playback Anssi Kostiainen via GitHub
• Re: [remote-playback] Add a section about browser initiated remote playback Philip Jägenstedt via GitHub
• Re: [remote-playback] Add a section about browser initiated remote playback Mounir Lamouri via GitHub
• Re: [remote-playback] Add a section about browser initiated remote playback François Daoust via GitHub
• Second Screen Working Group Revised Charter Approved; Join Second Screen Working Group (Call for Participation) Xueyuan Jia

Wednesday, 2 November 2016

• Re: [remote-playback] Add a section about browser initiated remote playback Anton Vayvod via GitHub
• [remote-playback] Pull Request: Add a section about browser initiated remote playback Anton Vayvod via GitHub
• Closed: [remote-playback] Getting availability and monitoring list of devices algorithms Anton Vayvod via GitHub
• [remote-playback] new commits pushed by avayvod Anton Vayvod via GitHub
• Re: [remote-playback] Update status section François Daoust via GitHub
• [remote-playback] new commits pushed by anssiko Anssi Kostiainen via GitHub
• Re: [remote-playback] SOTD updates to note stability and call for wide review (#58) Anton Vayvod via GitHub
• [remote-playback] Pull Request: SOTD updates to note stability and call for wide review (#58) François Daoust via GitHub
• Re: [remote-playback] Clarify availability monitoring Mounir Lamouri via GitHub

Tuesday, 1 November 2016

• Re: [remote-playback] Define what should happen when device gets disconnected while playing Anton Vayvod via GitHub
• Re: [remote-playback] Define what should happen when device gets disconnected while playing Anton Vayvod via GitHub
• Re: [remote-playback] Clarify availability monitoring Anton Vayvod via GitHub
• [remote-playback] Pull Request: Clarify availability monitoring Anton Vayvod via GitHub
• Re: [remote-playback] Getting availability and monitoring list of devices algorithms Anton Vayvod via GitHub
• [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" smaug---- via GitHub
• Re: [remote-playback] Update status section Anssi Kostiainen via GitHub

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