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

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

From: timeless <timeless@gmail.com>
Date: Wed, 16 Feb 2011 00:44:06 +0200
Message-ID: <AANLkTi=t26zUnUHA8HvmVkn166qB2Gg9knXb6W=8w_5g@mail.gmail.com>
2011/2/15 Leandro Graci? Gil <leandrogracia at chromium.org>:
> Given the above case, we don't think that the lifetime of the Stream objects
> should be controlled exclusively by the Web application. We think that the
> specification should state "the UA must allow the user to explicitly revoke
> access". The API should then be then extended with a way to handle
> gracefully the situation when access is revoked in the middle of a streaming
> session.
>
> All feedback will be greatly appreciated.

As long as UAs can replace the stream with a stream of compressed
solid black, i'm happy. I believe such a stream could probably have
very few frames (hopefully 2?).

With regard to being able to resume the stream, I think that's
something UAs could do w/o involving web apps.

For the case where the web app wants to turn off the stream, it's ok
to let the app ask to turn the stream back on, but otherwise, I don't
think I want a web app to be able to bother the user if the user has
chosen to turn mute the stream.
Received on Tuesday, 15 February 2011 14:44:06 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:30 UTC