Tuesday, 30 June 2015
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Switch to use rawgit.com to serve released WD
- Re: [presentation-api] Added Pictionary use case
- Re: [presentation-api] Update to messaging section
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Added Pictionary use case
Monday, 29 June 2015
- Re: [presentation-api] Define return value for cancelled/missing session for startSession/joinSession
- [presentation-api] Pull Request: Update to resuming requirement
- [presentation-api] Pull Request: Update to messaging section
- Re: [presentation-api] Define return value for cancelled/missing session for startSession/joinSession
- Re: [presentation-api] Define return value for cancelled/missing session for startSession/joinSession
Friday, 26 June 2015
- Re: [presentation-api] Necessity of an additional state to indicate a session was resumed
- Re: [presentation-api] Define return value for cancelled/missing session for startSession/joinSession
- Re: [presentation-api] Necessity of an additional state to indicate a session was resumed
- Closed: [presentation-api] Necessity of an additional state to indicate a session was resumed
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] A few typos and links to term definitions fixed
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Update href for power saving requirement
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Issue #68: Use cases and Requirements document updated
- [presentation-api] Pull Request: A few typos and links to term definitions fixed
- Re: Timing of TAG review
- [presentation-api] new commits pushed by anssiko
- [presentation-api] new commits pushed by anssiko
- [presentation-api] new commits pushed by anssiko
- Re: [presentation-api] Review the use cases and requirements
- [presentation-api] Pull Request: Issue #68: Use cases and Requirements document updated
- Closed: [presentation-api] Timing of availablechange event to signal screen availability
- Re: [presentation-api] Timing of availablechange event to signal screen availability
- Re: [presentation-api] Define reconnection for cross-page navigation on presenting user agent
- Re: [presentation-api] [meta] Working Draft publication requirements
- Re: [presentation-api] Section " Messaging between presentation sessions" should be updated
- Re: [presentation-api] Specify the NavigatorPresentation.session attribute and its related algorithms
- Closed: [presentation-api] Specify the NavigatorPresentation.session attribute and its related algorithms
Thursday, 25 June 2015
- [presentation-api] new commits pushed by mfoltzgoogle
- Closed: [presentation-api] Specify the presentation initialization algorithm
- Closed: [presentation-api] Make the Example section more concise
- Re: [presentation-api] Update references in Terminology; editorial changes in SoTD, Introduction, Examples, Common idioms; rewording Availability
- Re: [presentation-api] Update references in Terminology; editorial changes in SoTD, Introduction, Examples, Common idioms; rewording Availability
Wednesday, 24 June 2015
Tuesday, 23 June 2015
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Reference WebIDL for DOMException instead of DOM
- [presentation-api] Pull Request: Reference WebIDL for DOMException instead of DOM
- Re: [presentation-api] [meta] Working Draft publication requirements
- [presentation-api] Pull Request: Update references in Terminology; editorial changes in Examples
- Re: [presentation-api] [meta] Working Draft publication requirements
- [presentation-api] [meta] Working Draft publication requirements
Monday, 22 June 2015
- Re: [presentation-api] Updated version of PR#119: Initial description of session creation and monitoring in presenting
- CfC: publish the Presentation API as WD and initiate wider review; respond by 29 June
- Re: Timing of TAG review
- Re: [presentation-api] Updated version of PR#119: Initial description of session creation and monitoring in presenting
Friday, 19 June 2015
Thursday, 18 June 2015
- Re: Timing of TAG review
- Re: [presentation-api] Updated version of PR#119: Initial description of session creation and monitoring in presenting
- Re: [presentation-api] Updated version of PR#119: Initial description of session creation and monitoring in presenting
- [presentation-api] Pull Request: Updated version of PR#119: Initial description of session creation and monitoring in presenting
- Re: [presentation-api] Initial description of session creation and monitoring in presenting …
- [presentation-api] Section " Messaging between presentation sessions" should be updated
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Second version of Issue #9: How to filter available screens according to the content being presented
- Re: [presentation-api] Second version of Issue #9: How to filter available screens according to the content being presented
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Fix send algorithm
Wednesday, 17 June 2015
- Re: [presentation-api] fix send algorithm
- Re: [presentation-api] Second version of Issue #9: How to filter available screens according to the content being presented
- Re: [presentation-api] fix send algorithm
- [presentation-api] Pull Request: fix send algorithm
- [presentation-api] Pull Request: Initial description of session creation and monitoring in presenting …
- [presentation-api] Pull Request: Second version of Issue #9: How to filter available screens according to the content being presented
Tuesday, 16 June 2015
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Separate interface for controlling page and presenting page
- Re: [presentation-api] Security and privacy evaluation and considerations
- [presentation-api] new commits pushed by anssiko
Monday, 15 June 2015
- 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] Specify the presentation initialization algorithm
- Re: [presentation-api] Specify the presentation initialization algorithm
- [presentation-api] Spec authoring tool migration
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
Friday, 12 June 2015
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Resumption of multiple sessions
- Closed: [presentation-api] Resumption of multiple sessions
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Closed: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Issue #46: Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Specify the presentation initialization algorithm
- Re: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts
- Re: [presentation-api] Spec pubrules and Echidna compliant, WD generation semi-automated
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Spec pubrules and Echidna compliant, WD generation semi-automated
- [presentation-api] Pull Request: Issue 9: How to filter available screens according to the content being presented
Thursday, 11 June 2015
- Re: 答复: second screen use case provided from Tencent.
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Next F2F & TPAC 2015 Registration Now Open
- Re: [presentation-api] Review the use cases and requirements
- 答复: second screen use case provided from Tencent.
Wednesday, 10 June 2015
- Re: [presentation-api] Update the Status section, note stability per section
- Re: Moving the new publication process
- [presentation-api] Pull Request: Spec pubrules and Echidna compliant, WD generation semi-automated
- [presentation-api] Update the Status section, note stability per section
- Re: [presentation-api] Use HTTPS where possible
- [presentation-api] new commits pushed by anssiko
- [presentation-api] Pull Request: Stylesheet tweaks
- Cross-references database (xref) repository changed
- [presentation-api] Pull Request: Use HTTPS where possible
Tuesday, 9 June 2015
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Issue #39: Drop presentationId from startSession
- Re: [presentation-api] Issue #39: Drop presentationId from startSession
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Issue #39: Drop presentationId from startSession
- [presentation-api] Pull Request: Issue #39: Drop presentationId from startSession
- [presentation-api] Pull Request: Update cross references to align with whatwg/xrefs
- Re: Moving the new publication process
- Closed: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense
- Re: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense
- Closed: [presentation-api] URL schemes supported in presentation API
- Re: [presentation-api] URL schemes supported in presentation API
- Closed: [presentation-api] Define (cross) origin relationship between controller and presentation
- Re: [presentation-api] Define (cross) origin relationship between controller and presentation
- Closed: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- [presentation-api] new commits pushed by mfoltzgoogle
- Closed: [presentation-api] Make the "set of presentations" variable global
- Re: [presentation-api] Simplify algorithm prose for starting, joining, establishing connection; use common idioms
- Re: Moving the new publication process
- Re: Moving the new publication process
- Re: Timing of TAG review
- Re: Timing of TAG review
- Re: [presentation-api] Make the "set of presentations" variable global
- [presentation-api] Pull Request: Simplify algorithm prose for starting, joining, establishing connection; use common idioms
- Moving the new publication process
- Re: CfC: to use the new publication process; deadline June 8th
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Rethinking availability monitoring
Monday, 8 June 2015
- Re: [presentation-api] Rethinking availability monitoring
- Closed: [presentation-api] Fix bugs related to PresentationSession.url attribute
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] Pull Request: Fixes #102: Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Make the "set of presentations" variable global
- Re: Timing of TAG review
- Re: Timing of TAG review
- 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: Timing of TAG review
- Re: Timing of TAG review
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
Sunday, 7 June 2015
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Provide a better definition for the global set of presentations.
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
Friday, 5 June 2015
- Timing of TAG review
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Provide a better definition for the global set of presentations.
- [presentation-api] Pull Request: Set presentations issue 65
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: CfC: to use the new publication process; deadline June 8th
Thursday, 4 June 2015
- F2F resolutions (was: F2F minutes, proposed resolutions & actions)
- Re: [presentation-api] Specify the presentation initialization algorithm
- Re: [presentation-api] Presentations from within nested browsing contexts
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
Wednesday, 3 June 2015
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Issue #45: Security and Privacy Considerations
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Allow page to turn itself into a presentation session
- Re: [presentation-api] Separate interface for controlling page and presenting page
- Re: [presentation-api] Presentations from within nested browsing contexts
- Re: [presentation-api] Issue #45: Security and Privacy Considerations
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Security and privacy evaluation and considerations
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
Tuesday, 2 June 2015
- [presentation-api] Pull Request: Issue #45: Security and Privacy Considerations
- Following up on Action #04
- Re: Announcing the Presentation-Cast polyfill and slideshow demo
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: [presentation-api] Specify the presentation initialization algorithm
- Re: [presentation-api] Rethinking availability monitoring
- [presentation-api] Pull Request: Removed references to PresentationSession.url attribute (issue #102).
- [presentation-api] Fix bugs related to PresentationSession.url attribute
- Re: PresentationSession url attribute in startSession steps
- Re: [presentation-api] Investigate possible compatibility with HbbTV
- Re: PresentationSession url attribute in startSession steps
Monday, 1 June 2015
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Fix bugs in availablechange event
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense
- [presentation-api] Pull Request: Fix bugs in availablechange event
- Re: [presentation-api] Separate interface for controlling page and presenting page
- [presentation-api] Pull Request: Provide a better definition for the global set of presentations.
- Re: [presentation-api] Review the use cases and requirements
- Closed: [presentation-api] Define a Multiplayer Gaming Use Case
- Re: [presentation-api] Define a Multiplayer Gaming Use Case
- [presentation-api] new commits pushed by mfoltzgoogle
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Issue 68
- [presentation-api] new commits pushed by mfoltzgoogle
- Re: [presentation-api] Add NOTE clarifying presentation URL scheme support
- [presentation-api] Define behavior of Window and Fullscreen APIs in the presentation browsing context
- Re: [presentation-api] Review the use cases and requirements
- [presentation-api] Pull Request: Issue 68
- PresentationSession url attribute in startSession steps
- Re: [presentation-api] Rethinking availability monitoring
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Multiple presentation devices
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] URL schemes supported in presentation API
- Re: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense
- Re: [presentation-api] Provide session lifecycle management for presenting page
- Re: [presentation-api] Conformance classes definition
- Re: [presentation-api] Separate interface for controlling page and presenting page
- 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] Update requirements for multiple controllers and presentations
- Re: [presentation-api] Review the use cases and requirements
- Re: [presentation-api] Update requirements for multiple controllers and presentations