Re: [whatwg] File inputs, @accept, and expected behavior

2011-02-08 Thread Rich Tibbett
Tab Atkins Jr. wrote: The file input gained the @accept attribute a little while ago, to indicate what type of file should be accepted. It has three special values, image/*, video/*, and audio/*. I believe one intent of these special values is that browsers may offer the user the ability to

Re: [whatwg] File inputs, @accept, and expected behavior

2011-02-08 Thread Tab Atkins Jr.
On Tue, Feb 8, 2011 at 1:41 AM, Rich Tibbett ri...@opera.com wrote: Tab Atkins Jr. wrote: The file input gained the @accept attribute a little while ago, to indicate what type of file should be accepted.  It has three special values, image/*, video/*, and audio/*. I believe one intent of

Re: [whatwg] File inputs, @accept, and expected behavior

2011-02-08 Thread Bjartur Thorlacius
On 2/8/11, Tab Atkins Jr. jackalm...@gmail.com wrote: Right now it's entirely unobvious that UAs should even *think* about offering the functionality to record a file, so I think it would be useful. It's unobvious to me that UAs need to offer the functionality specifically, rather than rely on

[whatwg] File inputs, @accept, and expected behavior

2011-02-02 Thread Tab Atkins Jr.
The file input gained the @accept attribute a little while ago, to indicate what type of file should be accepted. It has three special values, image/*, video/*, and audio/*. I believe one intent of these special values is that browsers may offer the user the ability to capture an