- From: <bugzilla@jessica.w3.org>
- Date: Sun, 24 Nov 2013 02:10:09 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23820
--- Comment #6 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
(In reply to Travis Leithead [MSFT] from comment #5)
> (In reply to Silvia Pfeiffer from comment #4)
> > 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.
>
> It seems to me that if you're comfortable being able to use the concept of
> maximum/minimum at all, then you've already allowed for the possibility of
> not guaranteeing a consistent experience across a variety of devices, right?
No. I am trying to get the best possible experience to the user. If the user
has a camera that is capable of 720p, then I want to make use of that
capability. If the user has a camera that is only capable of 640x480, then I'll
accept that. I can't require 720p ("mandatory"), because in the second case, it
will fail and I won't get any video.
> It follows that if you're OK with variability in the
> experience, then being able to politely ask for the best possible experience
> via "optional" or "preference" input is about the same guarantee.
I don't want to have to specify all possible high camera resolutions in the
optional constraints from top to bottom as optional constraints, just to be
missing the odd one out of the particular camera model that a user has and then
end up providing whatever default the browser has (Chrome defaults to 640x480).
Instead, I want the browser to go, find out what the best possible resolution
of the camera is, and give that to me. How do you want that to be specified?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Sunday, 24 November 2013 02:10:11 UTC