RE: Two more issues for the tracker

Hi Anssi,

I don't have concrete use cases in mind I agree to close the issue for now. I like your comparison with @accept/@type attributes :)

Best regards,
Louay

> -----Original Message-----
> From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com]
> Sent: Mittwoch, 17. September 2014 15:51
> To: Bassbouss, Louay
> Cc: mark a. foltz; public-webscreens@w3.org; Anton Vayvod; Yuri Wiitala;
> Derek Cheng
> Subject: Re: Two more issues for the tracker
> 
> Hi Louay,
> 
> On 15 Sep 2014, at 17:44, Bassbouss, Louay
> <louay.bassbouss@fokus.fraunhofer.de> wrote:
> 
> > [Louay] maybe we can introduce some preferred parameters (instead of
> filter parameters) that may influence the order of the available screens in the
> selection dialog.
> 
> We'd need use cases to understand what would make a useful set of hints.
> Unless we have strong use cases for this, I'd propose we'll close the issue
> #22 [1] now and revisit it later as needed.
> 
> @accept hint of the <input> comes to my mind when I try to think of
> precedence on the web platform. Depending on the UA, the following is
> supposed to open up a file picker dialog which makes it easier to pick images
> from the file system (falling back to no filter applied if the UA does not
> understand @accept):
> 
> <input type="file" accept="image/*">
> 
> Another similarish attempt is @type on the <source> in which the MIME type
> as well as the preferred codec can be defined so that the UA can optimize by
> fetching the media resource it is likely able to understand. I believe this
> design has its issues though.
> 
> Thanks,
> 
> -Anssi
> 
> https://github.com/webscreens/presentation-api/issues/22

Received on Wednesday, 17 September 2014 14:15:30 UTC