- From: <bugzilla@jessica.w3.org>
- Date: Fri, 22 Nov 2013 00:42:49 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23820
--- Comment #4 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to Travis Leithead [MSFT] from comment #3)
> (In reply to Silvia Pfeiffer from comment #2)
>
> > mandatory: {
> > { frameRate: "maxPossible" }
>
> I'm actually not really sure what these values mean in the context of a
> mandatory constraint. Since (in theory) they can _always_ be satisfied,
> aren't they the same thing as an "optional" constraint? Perhaps we don't
> need them for mandatory constraints...?
Maybe.... but how do you guarantee to the Web Dev that you're providing the
maximum frameRate that is possible with the given camera? If you put that into
"optional", the browser is free to ignore it and return the smallest frameRate.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Friday, 22 November 2013 00:42:51 UTC