[Bug 23820] Add special values for PropertyValueRange to enable preference specification in optional constraints

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23820

--- Comment #5 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(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?
(Otherwise, you would have specified an exact value as a mandatory constraint.)
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. The only difference I can see
is whether you think the Browser is out to get you by not granting your polite
requests. Why would a browser _not_ try to satisfy your preferences, in order?

It seems counter-productive to assume that if you set some options/preferences,
that the browser probably won't give you them...? I would assume that the
browser will make a best-effort to grant them! (That's how I'd code up this
feature anyway.) 

Without any options/preferences set _at all_ then the browser is free to
fallback to defaults which may/may not be what you want.

-- 
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 01:52:09 UTC