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

RE: Question about HTML Media Capture specification

From: Jimenez, Ernesto, VF-Group <Ernesto.Jimenez@vodafone.com>
Date: Mon, 4 Jul 2011 14:59:15 +0200
Message-ID: <09C3F9F1A21FF546B312200CFA69F53B02BC9B09@VF-MBX20.internal.vodafone.com>
To: "Dominique Hazael-Massieux" <dom@w3.org>
Cc: <js45.yang@samsung.com>, <Ilkka.Oksanen@nokia.com>, <public-device-apis@w3.org>, 정상욱 <sangwook@samsung.com>, 이원석 <wonsuk11.lee@samsung.com>, 김규영 <gyuyoung.kim@samsung.com>
> -----Original Message-----
> From: Dominique Hazael-Massieux [mailto:dom@w3.org]
> Le lundi 04 juillet 2011 à 13:36 +0200, Jimenez, Ernesto, VF-Group a écrit :
> > What is the reason for having camera/camcorder/microphone as capture
> > options when they correlate 1 to 1 with the image/video/audio accept
> > values?
> Well, you can get pictures from both a camera or a camcorder; likewise, you
> can record sound from a camcorder.

Yes, but the developer doesn't know what options are available in the device. What would be the use case for me as a developer to specify I want to record audio from the camcorder instead of the microphone?

I would understand having options such as capture="front-facing-camera" and capture="rear-facing-camera". I understand the use case: a web app about photography would probably default to rear-facing camera, but a form to submit your profile photo would default to the front-facing one.

However, I don't understand why I would want to take a picture from the camcorder. Could you elaborate on that? :)


Received on Monday, 4 July 2011 12:59:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:29 UTC