public-secondscreen@w3.org from June 2015 by subject

[presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense

[presentation-api] [meta] Working Draft publication requirements

[presentation-api] A few typos and links to term definitions fixed

[presentation-api] Add NOTE clarifying presentation URL scheme support

[presentation-api] Added Pictionary use case

[presentation-api] Allow page to turn itself into a presentation session

[presentation-api] Conformance classes definition

[presentation-api] Define (cross) origin relationship between controller and presentation

[presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts

[presentation-api] Define a Multiplayer Gaming Use Case

[presentation-api] Define behavior of Window and Fullscreen APIs in the presentation browsing context

[presentation-api] Define reconnection for cross-page navigation on presenting user agent

[presentation-api] Define return value for cancelled/missing session for startSession/joinSession

[presentation-api] Fix bugs in availablechange event

[presentation-api] Fix bugs related to PresentationSession.url attribute

[presentation-api] fix send algorithm

[presentation-api] Initial description of session creation and monitoring in presenting …

[presentation-api] Investigate possible compatibility with HbbTV

[presentation-api] Issue #39: Drop presentationId from startSession

[presentation-api] Issue #45: Security and Privacy Considerations

[presentation-api] Issue #68: Use cases and Requirements document updated

[presentation-api] Issue 68

[presentation-api] Make the "set of presentations" variable global

[presentation-api] Multiple presentation devices

[presentation-api] Necessity of an additional state to indicate a session was resumed

[presentation-api] new commits pushed by anssiko

[presentation-api] new commits pushed by mfoltzgoogle

[presentation-api] Presentations from within nested browsing contexts

[presentation-api] Provide a better definition for the global set of presentations.

[presentation-api] Provide session lifecycle management for presenting page

[presentation-api] Pull Request: A few typos and links to term definitions fixed

[presentation-api] Pull Request: Added Pictionary use case

[presentation-api] Pull Request: Fix bugs in availablechange event

[presentation-api] Pull Request: Fix send algorithm

[presentation-api] Pull Request: Fixes #102: Fix bugs related to PresentationSession.url attribute

[presentation-api] Pull Request: Initial description of session creation and monitoring in presenting …

[presentation-api] Pull Request: Issue #39: Drop presentationId from startSession

[presentation-api] Pull Request: Issue #45: Security and Privacy Considerations

[presentation-api] Pull Request: Issue #46: Define a bi-directional data channel between opening and presenting browsing contexts

[presentation-api] Pull Request: Issue #68: Use cases and Requirements document updated

[presentation-api] Pull Request: Issue 68

[presentation-api] Pull Request: Issue 9: How to filter available screens according to the content being presented

[presentation-api] Pull Request: Provide a better definition for the global set of presentations.

[presentation-api] Pull Request: Reference WebIDL for DOMException instead of DOM

[presentation-api] Pull Request: Removed references to PresentationSession.url attribute (issue #102).

[presentation-api] Pull Request: Second version of Issue #9: How to filter available screens according to the content being presented

[presentation-api] Pull Request: Set presentations issue 65

[presentation-api] Pull Request: Simplify algorithm prose for starting, joining, establishing connection; use common idioms

[presentation-api] Pull Request: Spec pubrules and Echidna compliant, WD generation semi-automated

[presentation-api] Pull Request: Stylesheet tweaks

[presentation-api] Pull Request: Switch to use rawgit.com to serve released WD

[presentation-api] Pull Request: Update cross references to align with whatwg/xrefs

[presentation-api] Pull Request: Update href for power saving requirement

[presentation-api] Pull Request: Update references in Terminology; editorial changes in Examples

[presentation-api] Pull Request: Update to messaging section

[presentation-api] Pull Request: Update to resuming requirement

[presentation-api] Pull Request: Updated version of PR#119: Initial description of session creation and monitoring in presenting

[presentation-api] Pull Request: Use HTTPS where possible

[presentation-api] Reference WebIDL for DOMException instead of DOM

[presentation-api] Resumption of multiple sessions

[presentation-api] Rethinking availability monitoring

[presentation-api] Review the use cases and requirements

[presentation-api] Second version of Issue #9: How to filter available screens according to the content being presented

[presentation-api] Section " Messaging between presentation sessions" should be updated

[presentation-api] Security and privacy evaluation and considerations

[presentation-api] Separate interface for controlling page and presenting page

[presentation-api] Simplify algorithm prose for starting, joining, establishing connection; use common idioms

[presentation-api] Spec authoring tool migration

[presentation-api] Spec pubrules and Echidna compliant, WD generation semi-automated

[presentation-api] Specify behavior when multiple controlling pages are connected to the session

[presentation-api] Specify the NavigatorPresentation.session attribute and its related algorithms

[presentation-api] Specify the presentation initialization algorithm

[presentation-api] Timing of availablechange event to signal screen availability

[presentation-api] Update references in Terminology; editorial changes in Examples

[presentation-api] Update references in Terminology; editorial changes in SoTD, Introduction, Examples, Common idioms; rewording Availability

[presentation-api] Update requirements for multiple controllers and presentations

[presentation-api] Update the Status section, note stability per section

[presentation-api] Update to messaging section

[presentation-api] Updated version of PR#119: Initial description of session creation and monitoring in presenting

[presentation-api] URL schemes supported in presentation API

[presentation-api] Use HTTPS where possible

Announcing the Presentation-Cast polyfill and slideshow demo

CfC: publish the Presentation API as WD and initiate wider review; respond by 29 June

CfC: to use the new publication process; deadline June 8th

Closed: [presentation-api] "Queue a task to fire an event named statechange at s.onstatechange. " makes no sense

Closed: [presentation-api] Define (cross) origin relationship between controller and presentation

Closed: [presentation-api] Define a bi-directional data channel between opening and presenting browsing contexts

Closed: [presentation-api] Define a Multiplayer Gaming Use Case

Closed: [presentation-api] Fix bugs related to PresentationSession.url attribute

Closed: [presentation-api] Make the "set of presentations" variable global

Closed: [presentation-api] Make the Example section more concise

Closed: [presentation-api] Necessity of an additional state to indicate a session was resumed

Closed: [presentation-api] Resumption of multiple sessions

Closed: [presentation-api] Rethinking availability monitoring

Closed: [presentation-api] Specify the NavigatorPresentation.session attribute and its related algorithms

Closed: [presentation-api] Specify the presentation initialization algorithm

Closed: [presentation-api] Timing of availablechange event to signal screen availability

Closed: [presentation-api] URL schemes supported in presentation API

Cross-references database (xref) repository changed

F2F resolutions (was: F2F minutes, proposed resolutions & actions)

Following up on Action #04

Moving the new publication process

Next F2F & TPAC 2015 Registration Now Open

PresentationSession url attribute in startSession steps

Timing of TAG review

答复: second screen use case provided from Tencent.

Last message date: Tuesday, 30 June 2015 22:14:32 UTC