W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] Device element and the lifetime of the stream objects

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 16 Feb 2011 13:36:28 +0100
Message-ID: <op.vqzxa2fn64w2qv@anne-van-kesterens-macbook-pro.local>
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/
Received on Wednesday, 16 February 2011 04:36:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:04 UTC