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

Anne van Kesteren via GitHub

• Re: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor (Wednesday, 30 November)
• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts (Wednesday, 30 November)
• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts (Wednesday, 30 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Tuesday, 29 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Tuesday, 29 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Wednesday, 23 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Wednesday, 23 November)
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. (Tuesday, 22 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Tuesday, 22 November)
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. (Tuesday, 22 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Tuesday, 15 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Tuesday, 15 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Monday, 14 November)
• [presentation-api] [SameObject] for receiver seems wrong (Wednesday, 9 November)

Anssi Kostiainen via GitHub

• Re: [remote-playback] Add a section about browser initiated remote playback (Thursday, 3 November)
• [remote-playback] new commits pushed by anssiko (Wednesday, 2 November)
• Re: [remote-playback] Update status section (Tuesday, 1 November)

Anton Vayvod via GitHub

• Closed: [remote-playback] Evaluate Security and Privacy impacts (Wednesday, 30 November)
• Re: [remote-playback] Evaluate Security and Privacy impacts (Wednesday, 30 November)
• Re: [remote-playback] Add a privacy and security section (Wednesday, 30 November)
• [remote-playback] Pull Request: Add a privacy and security section (Wednesday, 30 November)
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Wednesday, 16 November)
• Closed: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Wednesday, 16 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Friday, 11 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Friday, 11 November)
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Friday, 11 November)
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm (Friday, 11 November)
• [remote-playback] new commits pushed by avayvod (Saturday, 5 November)
• [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Saturday, 5 November)
• [remote-playback] Merge steps 5 and 9 for prompt() algorithm (Friday, 4 November)
• [remote-playback] new commits pushed by avayvod (Friday, 4 November)
• Re: [remote-playback] prompt() should not be rejected if the state was connected when called (Thursday, 3 November)
• Re: [remote-playback] Add a section about browser initiated remote playback (Wednesday, 2 November)
• [remote-playback] Pull Request: Add a section about browser initiated remote playback (Wednesday, 2 November)
• Closed: [remote-playback] Getting availability and monitoring list of devices algorithms (Wednesday, 2 November)
• [remote-playback] new commits pushed by avayvod (Wednesday, 2 November)
• Re: [remote-playback] SOTD updates to note stability and call for wide review (#58) (Wednesday, 2 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Tuesday, 1 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Tuesday, 1 November)
• Re: [remote-playback] Clarify availability monitoring (Tuesday, 1 November)
• [remote-playback] Pull Request: Clarify availability monitoring (Tuesday, 1 November)
• Re: [remote-playback] Getting availability and monitoring list of devices algorithms (Tuesday, 1 November)

Francois Daoust

• Re: Publish a new Candidate Recommendation for Presentation API? (Tuesday, 22 November)
• Remote Playback API reviews requested (Wednesday, 9 November)
• New Working Draft of Remote Playback API published (Monday, 7 November)

François Daoust via GitHub

• Re: [presentation-api] Clarify event order when establishing a presentation connection (Tuesday, 29 November)
• Re: [presentation-api] Clarifies inputs to algorithms. (Tuesday, 29 November)
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. (Tuesday, 29 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Wednesday, 23 November)
• Re: [presentation-api] Clarify identities of PresentationConnection objects in reconnect() steps (Tuesday, 22 November)
• Re: [presentation-api] Clarify the task source for the specification. (Tuesday, 22 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Tuesday, 22 November)
• [presentation-api] Well defined environment for nested contexts of the receiving browsing context? (Wednesday, 16 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Wednesday, 16 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Tuesday, 15 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Tuesday, 15 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Tuesday, 15 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Monday, 14 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Monday, 14 November)
• [remote-playback] Evaluate Security and Privacy impacts (Wednesday, 9 November)
• [remote-playback] Internationalization considerations (Wednesday, 9 November)
• Closed: [remote-playback] Update status section (Monday, 7 November)
• Re: [remote-playback] Update status section (Monday, 7 November)
• [remote-playback] new commits pushed by tidoust (Monday, 7 November)
• Re: [remote-playback] Add a section about browser initiated remote playback (Thursday, 3 November)
• Re: [remote-playback] Update status section (Wednesday, 2 November)
• [remote-playback] Pull Request: SOTD updates to note stability and call for wide review (#58) (Wednesday, 2 November)

Kostiainen, Anssi

• Re: New Working Draft of Remote Playback API published (Monday, 7 November)

Louay Bassbouss via GitHub

• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous (Saturday, 5 November)

mark a. foltz

• Re: Publish a new Candidate Recommendation for Presentation API? (Wednesday, 30 November)
• Publish a new Candidate Recommendation for Presentation API? (Tuesday, 22 November)

Mark Foltz via GitHub

• Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts (Wednesday, 30 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Wednesday, 30 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Tuesday, 29 November)
• [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts (Tuesday, 29 November)
• Closed: [presentation-api] Clarify arguments to getting presentation displays availability information (Tuesday, 29 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 29 November)
• [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor (Tuesday, 29 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 29 November)
• [presentation-api] Pull Request: Clarifies inputs to algorithms. (Monday, 28 November)
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. (Monday, 28 November)
• [presentation-api] Pull Request: Move mixed content check to PresentationRequest ctor. (Monday, 28 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Monday, 28 November)
• Closed: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous (Monday, 28 November)
• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous (Monday, 28 November)
• 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" (Monday, 28 November)
• 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" (Monday, 28 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Monday, 28 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Monday, 28 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Monday, 28 November)
• Closed: [presentation-api] define the behavior for consecutive |getAvailability| (Monday, 28 November)
• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. (Monday, 28 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Monday, 28 November)
• Closed: [presentation-api] [SameObject] for receiver seems wrong (Monday, 28 November)
• Re: [presentation-api] Remove [SameObject] from navigator.presentation.receiver (Monday, 28 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Monday, 28 November)
• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. (Thursday, 24 November)
• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous (Wednesday, 23 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 23 November)
• Closed: [presentation-api] Use USVString for URLs (Wednesday, 23 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 23 November)
• Re: [presentation-api] Adds steps for initiating presentation from default presentation request. (Tuesday, 22 November)
• Closed: [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection (Tuesday, 22 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Tuesday, 22 November)
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. (Tuesday, 22 November)
• Re: [presentation-api] Clarify event order when establishing a presentation connection (Tuesday, 22 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Tuesday, 22 November)
• Re: [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection (Tuesday, 22 November)
• [presentation-api] Pull Request: Clarify identities of PresentationConnection objects in reconnect() steps (Tuesday, 22 November)
• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Monday, 21 November)
• Re: [presentation-api] Clarify arguments to getting presentation displays availability information (Monday, 21 November)
• Re: [presentation-api] Well defined environment for nested contexts of the receiving browsing context? (Monday, 21 November)
• Re: [presentation-api] Remove [SameObject] from navigator.presentation.receiver (Monday, 21 November)
• [presentation-api] Pull Request: Remove [SameObject] from navigator.presentation.receiver (Monday, 21 November)
• Re: [presentation-api] [SameObject] for receiver seems wrong (Monday, 21 November)
• [presentation-api] Determine if we need to fire a terminated event in the receiving browsing context(s) (Monday, 21 November)
• Re: [presentation-api] Clarify when a simultaneous call to start() can be rejected. (Monday, 21 November)
• [presentation-api] Pull Request: Clarify when a simultaneous call to start() can be rejected. (Monday, 21 November)
• 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" (Monday, 21 November)
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest URLs. (Monday, 21 November)
• Re: [presentation-api] Replace DOMString with USVString for PresentationRequest url and id. (Monday, 21 November)
• [presentation-api] Pull Request: Replace DOMString with USVString for PresentationRequest url and id. (Saturday, 19 November)
• Re: [presentation-api] Clarify the task source for the specification. (Saturday, 19 November)
• [presentation-api] Pull Request: Clarify the task source for the specification. (Saturday, 19 November)
• Re: [presentation-api] Clarifies the roles of objects for getting presentation display availability. (Friday, 18 November)
• [presentation-api] Pull Request: Clarifies the roles of objects for getting presentation display availability (Friday, 18 November)
• Re: [presentation-api] Adds steps for initiating presentation from default presentation request. (Friday, 18 November)
• [presentation-api] Pull Request: Adds steps for initiating presentation from default presentation request. (Friday, 18 November)
• Closed: [presentation-api] setConnection in example 5.5 may put UI in an inconsistent state (Wednesday, 16 November)
• Re: [presentation-api] setConnection in example 5.5 may put UI in an inconsistent state (Wednesday, 16 November)
• [presentation-api] new commits pushed by mfoltzgoogle (Wednesday, 16 November)
• [presentation-api] Pull Request: A couple of small fixes to the example code (Wednesday, 16 November)
• [presentation-api] Steps to reconnect to a presentation assume there's already a PresentationConnection (Saturday, 12 November)
• Re: [presentation-api] "setting presentation.defaultRequest will have no effect" note is ambiguous (Tuesday, 8 November)
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Tuesday, 8 November)
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm (Tuesday, 8 November)
• Re: [presentation-api] [meta] Presentation API Testing (Thursday, 3 November)

Mike West via GitHub

• Re: [presentation-api] Consider checking for security context in the PresentationRequest constructor (Wednesday, 23 November)

Mounir Lamouri via GitHub

• Re: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor (Wednesday, 30 November)
• Re: [presentation-api] Move mixed content check to PresentationRequest ctor. (Tuesday, 29 November)
• Closed: [remote-playback] prompt() should not be rejected if the state was connected when called (Thursday, 17 November)
• Re: [remote-playback] prompt() should not be rejected if the state was connected when called (Thursday, 17 November)
• Re: [remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions (Wednesday, 16 November)
• Closed: [remote-playback] Define interaction with setMediaKeys() / Encrypted Media Extensions (Wednesday, 16 November)
• Closed: [remote-playback] Use [SameObject] for HTMLMediaElement#remote (Wednesday, 16 November)
• [remote-playback] new commits pushed by mounirlamouri (Wednesday, 16 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Saturday, 12 November)
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Saturday, 12 November)
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm (Saturday, 12 November)
• Re: [remote-playback] Merge steps 5 and 9 for prompt() algorithm (Friday, 11 November)
• Re: [remote-playback] Define what should happen when device gets disconnected while playing (Friday, 11 November)
• Re: [remote-playback] Make NotFoundError when prompt() is called and availability monitoring is not available optional (Friday, 11 November)
• [remote-playback] prompt() should not be rejected if the state was connected when called (Thursday, 3 November)
• Re: [remote-playback] Add a section about browser initiated remote playback (Thursday, 3 November)
• Re: [remote-playback] Clarify availability monitoring (Wednesday, 2 November)

Philip Jägenstedt via GitHub

• [remote-playback] Use [SameObject] for HTMLMediaElement#remote (Wednesday, 16 November)
• Re: [remote-playback] Add a section about browser initiated remote playback (Thursday, 3 November)

smaug---- 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" (Tuesday, 1 November)

Xueyuan Jia

• Second Screen Working Group Revised Charter Approved; Join Second Screen Working Group (Call for Participation) (Thursday, 3 November)

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