- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Sep 2016 12:09:16 +0000
- To: public-media-capture-logs@w3.org
@burnburn said "change the settings on its own as long as the
constraints continue to be satisfied".
@alvestrand said "if the new conditions mean that the present
constraints cannot be satisified, it MUST queue a task to fire an
"overconstrained" event"
Which is it?
FWIW Firefox implements the first for competing tabs at least. That
is, once you've managed to apply `{exact}` to a capability
successfully, another tab can't change it on you, or cause
`OverConstrainedError` on you, rather the other tab will fail to apply
its competing constraints.
We don't (currently) detect drops in `frameRate` due to lighting or
anything like that.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at
https://github.com/w3c/mediacapture-main/issues/394#issuecomment-246661185
using your GitHub account
Received on Tuesday, 13 September 2016 12:09:25 UTC