Friday, 29 May 2015
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- F2F Meeting in Berlin: Slides of the Open Session are available for download
Thursday, 28 May 2015
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Multiple presentation devices
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- [presentation-api] Multiple presentation devices
- Re: [presentation-api] URL schemes supported in presentation API
- Re: [presentation-api] Add NOTE clarifying presentation URL scheme support
- CfC: to use the new publication process; deadline June 5th
- Re: F2F minutes, proposed resolutions & actions
- Re: [presentation-api] Add NOTE clarifying presentation URL scheme support
Wednesday, 27 May 2015
- Re: [presentation-api] URL schemes supported in presentation API
- [presentation-api] Pull Request: Add NOTE clarifying presentation URL scheme support
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Review the use cases and requirements
- [presentation-api] Pull Request: Update requirements for multiple controllers and presentations
- [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense
Tuesday, 26 May 2015
- Re: F2F minutes, proposed resolutions & actions
- [presentation-api] Conformance classes definition
- Re: [presentation-api] Review the use cases and requirements
Monday, 25 May 2015
- [presentation-api] Provide session lifecycle management for presenting page
- [presentation-api] Separate interface for controlling page and presenting page
Wednesday, 20 May 2015
- F2F minutes, proposed resolutions & actions
- Re: [presentation-api] Presenting the content of an <audio> or <video> element
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] URL schemes supported in presentation API
- Re: [presentation-api] Presentations from within nested browsing contexts
- Re: [presentation-api] Presentations from within nested browsing contexts
- Re: [presentation-api] Allow page to designate a default presentation URL
- Re: [presentation-api] Allow page to designate a default presentation URL
- Re: [presentation-api] Resumption of multiple sessions
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Screen availability mechanism for multiple sessions
- Re: [presentation-api] How to filter available screens according to the content being presented
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Screen availability mechanism for multiple sessions
- Closed: [presentation-api] Screen availability mechanism for multiple sessions
- Re: [presentation-api] Define user agent context for rendering the presentation
- Re: [presentation-api] Presenting the content of an <audio> or <video> element
- F2F Day 1 draft minutes, proposed resolutions & actions
- Re: [presentation-api] Define user agent context for rendering the presentation
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Review the use cases and requirements
Tuesday, 19 May 2015
- Re: [presentation-api] Fixed typos and removed the 'origin' extraction step from the send() algorithm
- Call for Exclusions (Update): Presentation API
- Re: [presentation-api] Define user agent context for rendering the presentation
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Drop the 'presentation' concept, it is not used anywhere.
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Specify the presentation initialization algorithm
- Re: [presentation-api] Refine how to do session teardown/disconnect/closing
- Re: [presentation-api] Define security requirements for messaging channel between secure origins
- [presentation-api] Pull Request: Rethinking availability monitoring
- [presentation-api] Pull Request: Fixed typos and removed the 'origin' extraction step from the send() algorithm
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- Re: [presentation-api] Security and privacy evaluation and considerations
Monday, 18 May 2015
- Re: Request to alter order of the F2F agenda
- Re: Request to alter order of the F2F agenda
- Request to alter order of the F2F agenda
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- Re: F2F meeting logistics
Sunday, 17 May 2015
Friday, 15 May 2015
- Re: [presentation-api] Define algorithm for browser initiated presentation using default presentation URL
- Re: [presentation-api] Define algorithm for browser initiated presentation using default presentation URL
- Re: [presentation-api] default-presentation link type and browser initiated presentation algorithm
- [presentation-api] Pull Request: default-presentation link type and browser initiated presentation algorithm
- F2F meeting logistics
Thursday, 14 May 2015
- [presentation-api] Define algorithm for browser initiated presentation using default presentation URL
- Closed: [presentation-api] Allow page to designate a default presentation URL
- Re: [presentation-api] Allow page to designate a default presentation URL
- Re: [presentation-api] Added defaultsessionstart and default-presentation <link> to the spec
- [presentation-api] new commits pushed by mfoltzgoogle
Wednesday, 13 May 2015
Thursday, 14 May 2015
- Re: [presentation-api] Fixed the structure of <section> tags in the spec HTML
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Added defaultsessionstart and default-presentation <link> to the spec
- Re: [presentation-api] Fixed the structure of <section> tags in the spec HTML
- Re: [presentation-api] Define return value for cancelled/missing session for startSession/joinSession
- Re: [presentation-api] Define reconnection for cross-page navigation on presenting user agent
- Re: [presentation-api] Timing of availablechange event to signal screen availability
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
Wednesday, 13 May 2015
- Re: [presentation-api] Fixed the structure of <section> tags in the spec HTML
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Refine how to do session teardown/disconnect/closing
- Re: [presentation-api] Refine how to do session teardown/disconnect/closing
- Re: [presentation-api] Added defaultsessionstart and default-presentation <link> to the spec
- Re: [presentation-api] Added defaultsessionstart and default-presentation <link> to the spec
- Re: [presentation-api] Fixed the structure of <section> tags in the spec HTML
- [presentation-api] Pull Request: Fixed the structure of <section> tags in the spec HTML
- 1:n messaging use cases
- Re: Welcome to the Second Screen Presentation WG
- Re: [presentation-api] Rethinking availability monitoring
- Re: Welcome to the Second Screen Presentation WG
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- RE: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Welcome to the Second Screen Presentation WG
- Re: [presentation-api] Refine how to do session teardown/disconnect/closing
Tuesday, 12 May 2015
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Presenting the content of an <audio> or <video> element
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Rethinking availability monitoring
Monday, 11 May 2015
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Re: [presentation-api] Rethinking availability monitoring
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Security and privacy evaluation and considerations
- [presentation-api] Pull Request: 'data' is an attribute of the event
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Re: [presentation-api] Added defaultsessionstart and default-presentation <link> to the spec
- Re: [presentation-api] Rethinking availability monitoring
Friday, 8 May 2015
- Re: F2F Agenda for the F2F 19-20 May 2015 in Berlin
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Define (cross) origin relationship between opener and presenting page
Monday, 4 May 2015
Thursday, 7 May 2015
- Re: Proper sources for cross-references?
- Re: Proper sources for cross-references?
- Re: [presentation-api] Security and privacy evaluation and considerations