- From: Mark Watson <watsonm@netflix.com>
- Date: Thu, 11 Sep 2014 07:54:51 -0700
- To: Marco Chen <mchen@mozilla.com>
- Cc: "public-webscreens@w3.org" <public-webscreens@w3.org>
- Message-ID: <-7115709925130409026@unknownmsgid>
On Sep 10, 2014, at 8:42 PM, Marco Chen <mchen@mozilla.com> wrote: Hi Mark, Could you give any use case of why UA needs to filter screens regarding to requested URL? Yes, the user is visiting www.netflix.com and the UA discovers, using DIAL, a single remote SmartTV. This SmartTV has a YouTube app but no Netflix app. The user should not be shown the 'present' icon in this case. However, with the API as it stands, the Netflix site will receive the unavailablechange event and will show the 'present' icon. But when we call requestSession with a Netflix URL, it will fail because there is no Netflix app on the TV. ... Mark Thanks, Sincerely yours. ------------------------------ *From: *"Mark Watson" <watsonm@netflix.com> *To: *public-webscreens@w3.org *Sent: *Thursday, September 11, 2014 2:03:24 AM *Subject: *How to filter available screens according to the content being presented (issue #9) All, This issue is all about ensuring that the user is not presented with a "present" icon which, when clicked, does nothing because there are in fact no available screens supporting the content. The issue suggests one approach, whereby the UA can be instructed to filter the available screens to those supporting specific provided URLs. Another approach would be to provide a new method: Promise<bool> canRequestSession( DOMString url ); This would take exactly the same parameters as requestSession, but rather than prompting the user it would return a prediction of whether there would be any screens to prompt the user with. The application could avoid showing the "present" icon if there are in fact no suitable screens. ...Mark
Received on Thursday, 11 September 2014 14:55:20 UTC