[whatwg] Device element and the lifetime of the stream objects
Anne van Kesteren
annevk at opera.com
Wed Feb 16 04:36:28 PST 2011
On Tue, 15 Feb 2011 17:48:24 +0100, Leandro Graciá Gil
<leandrogracia at chromium.org> wrote:
> All feedback will be greatly appreciated.
This is just a thought. Instead of acquiring a Stream object
asynchronously there always is one available showing transparent black or
some such. E.g. navigator.cameraStream. It also inherits from EventTarget.
Then on the Stream object you have methods to request camera access which
triggers some asynchronous UI. Once granted an appropriately named event
is dispatched on Stream indicating you now have access to an actual
stream. When the user decides it is enough and turns of the camera (or
something else happens) some other appropriately named event is dispatched
on Stream again turning it transparent black again.
This also removes the need for the <device> element as has been mentioned
off-list. Basically, the idea was that <device> does not really help
anyone. It makes custom in-page UI harder, it does not prevent the need
for scripting, and it does not help with fallback.
This is somewhat weird though :-)
--
Anne van Kesteren
http://annevankesteren.nl/
More information about the whatwg
mailing list