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

Re: Question about HTML Media Capture specification

From: Kyle Huey <me@kylehuey.com>
Date: Mon, 27 Jun 2011 10:03:22 -0700
Message-ID: <BANLkTi=Lxxg=Ye=8W+dNMLihtSuFdzr7qg@mail.gmail.com>
To: Vivek Khurana <hiddenharmony@gmail.com>
Cc: Josh Soref <jsoref@rim.com>, "js45.yang@samsung.com" <js45.yang@samsung.com>, "Ilkka.Oksanen@nokia.com" <Ilkka.Oksanen@nokia.com>, "dom@w3.org" <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, 정상욱 <sangwook@samsung.com>, 이원석 <wonsuk11.lee@samsung.com>, 김규영 <gyuyoung.kim@samsung.com>
On Mon, Jun 27, 2011 at 9:55 AM, Vivek Khurana <hiddenharmony@gmail.com>wrote:

>  Above examples are bad from usability perspective and semantically
> wrong too. In all OSes 'Browse' button corresponds to file picker
> dialog. Launching Camera or Audio recorder on clicking 'Browse' will
> confuse the user.
>

This is not what Josh is proposing ....


>  To allow launching different interfaces from file input type, we
> should allow changing the value of the 'Browse' text. This way
> developer can call the camera capture or audio recorder file input
> button to 'Record' or anything which corresponds to the interface
> being triggered.
>

A whitelisted set of strings shipped with the UA might be ok, but this is
very much an implementation detail.

- Kyle
Received on Monday, 27 June 2011 17:03:51 GMT

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