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

Re: Question about HTML Media Capture specification

From: Vivek Khurana <hiddenharmony@gmail.com>
Date: Mon, 27 Jun 2011 22:25:34 +0530
Message-ID: <BANLkTikJyKWS8s965edasVo74+TObngojA@mail.gmail.com>
To: Josh Soref <jsoref@rim.com>
Cc: "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>
2011/6/27 Josh Soref <jsoref@rim.com>:

[snip]

>
> That's an implementation detail.
>
> Your average file picker button is "[ Browse... ]", but nothing prevents it from being:
>
> "[ 📷| Browse... ]", where clicking on 📷 triggers a Camera [1].
>

[snip]

> Your average file picker button is "[ Browse... ]", but nothing prevents it from being:
>
> "[ 🎤| Browse... ]", where clicking on 🎤 triggers an Audio Recorder [2].
>

[snip]

>
> Your average file picker button is "[ Browse... ]", but nothing prevents it from being:
>
> "[ 🎥 | Browse... ]", where clicking on 🎥 triggers a Movie Studio [3].
>

 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.
 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.

regards
Vivek

-- 
The hidden harmony is better than the obvious!!
Received on Monday, 27 June 2011 16:56:01 GMT

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