W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] Supporting scanners on the web

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 15 Oct 2013 00:21:05 +0000 (UTC)
To: Jonas Sicking <jonas@sicking.cc>
Message-ID: <alpine.DEB.2.00.1310150020490.11763@ps20323.dreamhostps.com>
Cc: Jeff Muizelaar <jmuizelaar@mozilla.com>, Benjamin Smedberg <benjamin@smedbergs.us>, Robert O'Callahan <robert@ocallahan.org>, WHAT Working Group <whatwg@whatwg.org>
On Mon, 14 Oct 2013, Jonas Sicking wrote:
> On Mon, Oct 14, 2013 at 3:33 PM, Ian Hickson <ian@hixie.ch> wrote:
> > On Mon, 30 Sep 2013, Benjamin Smedberg wrote:
> >>
> >> For now I intend to focus on implementing the scanning UI in the 
> >> browser and just handing the site the final product. Any thoughts of 
> >> exposing a fine-grained control over previews and incremental results 
> >> needs significantly more thought about how that would work on both 
> >> desktop and mobile devices.
> >
> > I'd recommend going with <input type=file accept=image/*> for now, and 
> > seeing where that gets us. We can always add attributes or an API if 
> > there's a real need for more control.
> 
> For what it's worth, I think the way I would do this in Firefox is to 
> add an addon hook for "image providers" (and maybe "video providers") 
> which would allow us to create an WebActiity/AndroidIntent-like chooser.

Yeah, that seems eminently reasonable.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 15 October 2013 00:21:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC