[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 #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(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...?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Tuesday, 19 November 2013 19:32:02 UTC