public-secondscreen@w3.org from December 2016 by subject

[presentation-api] [meta] Presentation API Testing

[presentation-api] Addresses Issues 382 and 383 on the steps to get presentation displays.

[presentation-api] Adds a note about display of origins that are not potentially trustworthy.

[presentation-api] Authenticity of screen selection permission is problematic in insecure contexts

[presentation-api] Check on Presentation display availability in getAvailability can never be true

[presentation-api] Clarify event order when establishing a presentation connection

[presentation-api] Drop step 6 of getAvailability for consistency with start?

[presentation-api] Filling out the list of available presentation displays for start

[presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor

[presentation-api] Issue #379: Adds sandboxing flag check to PresentationRequest ctor.

[presentation-api] Issue #387: Monitoring algo takes pending request to start into account

[presentation-api] Issue 387: Need to make sure we have a display list for start().

[presentation-api] Make select algo reject in ancestor and descendant browsing contexts

[presentation-api] Make sure all IDL members have "dfn" in prose

[presentation-api] Migrate HTML 5.0 references to HTML 5.1?

[presentation-api] new commits pushed by mfoltzgoogle

[presentation-api] Pull Request: Addreses Issue 387

[presentation-api] Pull Request: Addresses Issue #391

[presentation-api] Pull Request: Addresses Issue #394: Reject start() in all browsing contexts

[presentation-api] Pull Request: Addresses Issue #398: Sandboxing steps in start, reconnect, getAvailability are now useless

[presentation-api] Pull Request: Addresses Issues 382 and 383 on the steps to get presentation displays.

[presentation-api] Pull Request: Adds a note about display of origins that are not potentially trustworthy.

[presentation-api] Pull Request: Issue #360: Adds a presentation task source

[presentation-api] Pull Request: Issue #379: Adds sandboxing flag check to PresentationRequest ctor.

[presentation-api] Pull Request: Issue #387: Monitoring algo takes pending request to start into account

[presentation-api] Pull Request: Issue 387: Need to make sure we have a display list for start().

[presentation-api] Pull Request: Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason

[presentation-api] Pull Request: Sets the state of receiving presentation connections to terminated before unload.

[presentation-api] Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason

[presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless

[presentation-api] Sets the state of receiving presentation connections to terminated before unload.

[presentation-api] Step 11 of getAvailability should not run "in parallel"

[presentation-api] Steps that re-use objects should specify the relevant settings object/Javascript Realm

[presentation-api] Well defined environment for nested contexts of the receiving browsing context?

[presentation-api] Wrong use of "available presentation displays" in 6.4.4

[remote-playback] Internationalization considerations

Closed: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts

Closed: [presentation-api] Check on Presentation display availability in getAvailability can never be true

Closed: [presentation-api] Clarify event order when establishing a presentation connection

Closed: [presentation-api] Determine if we need to fire a terminated event in the receiving browsing context(s)

Closed: [presentation-api] Drop step 6 of getAvailability for consistency with start?

Closed: [presentation-api] Filling out the list of available presentation displays for start

Closed: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor

Closed: [presentation-api] Make select algo reject in ancestor and descendant browsing contexts

Closed: [presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless

Closed: [presentation-api] Step 11 of getAvailability should not run "in parallel"

Closed: [presentation-api] Steps that re-use objects should specify the relevant settings object/Javascript Realm

Closed: [presentation-api] Well defined environment for nested contexts of the receiving browsing context?

Closed: [presentation-api] Wrong use of "available presentation displays" in 6.4.4

Last message date: Tuesday, 27 December 2016 16:40:00 UTC