- From: timeless <timeless@gmail.com>
- Date: Thu, 14 Jul 2011 09:23:00 -0400
I'd expect a web app to have no idea about device camera specifications and thus to not be able to properly specify a flash duration. I don't see how such a thing is valuable. If a user is in a movie theater, or a museum, it's quite likely they won't notice a web app is forcing a flash. Let the user control flash through a useragent only or host application only mode. I believe the hazards of exposing flash duration outweigh any benefits. The only application class I know of built using control of camera flash is "flash-light", and that's both a hack and not guaranteed to be workable for all possible flash technologies. On 7/14/11, Shwetank Dixit <shwetankd at opera.com> wrote: > On Thu, 14 Jul 2011 04:09:40 +0530, Ian Hickson <ian at hixie.ch> wrote: > >> >>> Another question is flash. As far as I have seen, there seems to be no >>> option to specify whether the camera needs to use flash or not. Is this >>> decision left up to the device? (If someone is making an app which is >>> just clicking a picture of the person, then it would be nice to have the >>> camera use flash in low light conditions). >> getUserMedia() returns a video stream, so it wouldn't use a flash. > > Wouldn't it make sense to have a provision for flash separately then? I > think a lot of apps would like just a picture instead of video, and in > those cases, flash would be required. Maybe a seperate provision in the > spec which defines whether to use flash, and if so, for how many > miliseconds. Is that doable? > -- > Shwetank Dixit > Web Evangelist, > Site Compatibility / Developer Relations / Core Engineering Group > Member - W3C Mobile Web for Social Development (MW4D) Group > Member - Web Standards Project (WaSP) - International Liaison Group > Opera Software - www.opera.com > > Using Opera's revolutionary email client: http://www.opera.com/mail/ > -- Sent from my mobile device
Received on Thursday, 14 July 2011 06:23:00 UTC