W3C home > Mailing lists > Public > public-secondscreen@w3.org > July 2015

[presentation-api] Remove getAvailability() url argument unless implemented

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Tue, 07 Jul 2015 12:15:26 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-93517045-1436271323-sysbot+gh@w3.org>
foolip has just created a new issue for 
https://github.com/w3c/presentation-api:

== Remove getAvailability() url argument unless implemented ==
This method was mentioned in 
https://lists.w3.org/Archives/Public/public-secondscreen/2015Jul/0002.html

> The group notes that a generic true/false is not enough in many 
> situations where the URL to present may require additional 
capabilities. 
> That is the reason why the "getAvailability" function takes the URL 
to 
> present as parameter, to allow the user agent to filter screens.

As actually implemented in Blink, the method takes an argument but 
it's never used. Unless there is an implementation that intends to do 
something with the argument, it would be better to not have it. 
Otherwise there will be no way to feature detect when it's *actually* 
supported, as `Presentation.prototype.getAvailability.length` will 
already be 1.

Slightly off-topic, it's not clear to me what could actually be done 
with just a URL. Presumably one would have to actually try to load the
 URL, make a guess about what features it needs to render, and then 
match that against the capabilities of the platform?

See https://github.com/w3c/presentation-api/issues/138
Received on Tuesday, 7 July 2015 12:15:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 July 2015 12:15:28 UTC