W3C home > Mailing lists > Public > public-secondscreen@w3.org > February 2017

Re: [presentation-api] [meta] Publish a revised Candidate Recommendation

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Tue, 14 Feb 2017 18:39:49 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-279795674-1487097588-sysbot+gh@w3.org>
Here's a summary of the current state of the Chrome implementation (as
 of 58.0.3004.3, the current dev channel release):

# On desktop and Android releases
* Currently supports 2-UA mode using Chromecast, only with URLs that 
correspond to registered Cast applications.
* Support for `new PresentationRequest(DOMString[])` has landed; 
multiple URLs are accepted to construct the PresentationRequest.

# On the desktop release
* Support for 1-UA mode with arbitrary URLs has landed (both 
controller and receiver APIs).
  * We will send a demo link soon :-)

# Completed items from the PR exit criteria
* Implementations of controlling UA for 1UA and 2UA mode.
* Implementation of receiving UA for 1UA mode.
* Web platform tests mostly pass for these implementations, with the 
following exceptions:
  * `reconnect()` is not yet supported for 1UA presentations.  Expect 
to fix in M58. 
  * Some fail because of [incompatibility between idlharness.js and 
Blink 
bindings](https://bugs.chromium.org/p/chromium/issues/detail?id=643712).
  * There are a few bugs we are tracking down :-)

# "At risk"
* There are not many Web platform tests for the receiving UA.
* We plan on implementing the receiving UA in 2-UA mode at some point,
 but I am not sure it can be completed by the PR exit milestone of Q2 
2017.



-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/406#issuecomment-279795674
 using your GitHub account
Received on Tuesday, 14 February 2017 18:39:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 February 2017 18:39:56 UTC