W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2010

Re: Capture API question

From: Doug Turner <dougt@dougt.org>
Date: Fri, 11 Jun 2010 10:57:37 -0700
Cc: W3C Device APIs and Policy WG <public-device-apis@w3.org>, Robin Berjon <robin@robineko.com>, Dominique Hazael-Massieux <dom@w3.org>
Message-Id: <0A6E747C-3A4F-47FD-88C2-D5210642935B@dougt.org>
To: Andrei Popescu <andreip@google.com>
Hey Andrei,

How will the web developer know what to use?  What is the use case for the source param?

Doug

On Jun 11, 2010, at 10:54 AM, Andrei Popescu wrote:

> Hi Doug,
> 
> That's pretty much what we have. The only difference is the "source"
> param on the accept type.
> 
> Andrei
> 
> On Fri, Jun 11, 2010 at 6:51 PM, Doug Turner <dougt@dougt.org> wrote:
>> Hi All,
>> 
>> Mozilla is interested in the following.  For images and fixed length video (e.g. a video clip, not streaming.) we want this to work.
>> 
>> <input type="file" accept="image/*">
>> 
>> or
>> 
>> <input type="file" accept="video/*">
>> 
>> When the user clicks on the button assoicated with the input, a dialog will appear showing a live preview of their camera (and maybe a way to get to their file system pictures).  They will be able to take a screenshot or record.  When they are happy, they can click okay, and the data can be given to the page.  This follows the same security model that users are already comfortable with (namely the file picker).
>> 
>> And then the page can make use of the File API for data manipulation (file api ->  data uri (or reference) ->  canvas)
>> 
>> We have started an implementation based on this.
>> 
>> See bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=507749
>>          https://bugzilla.mozilla.org/show_bug.cgi?id=451674
>> 
>> Regards,
>> Doug Turner
> 
Received on Friday, 11 June 2010 17:58:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:10 GMT