- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Tue, 3 Dec 2013 20:53:32 +0000
- To: Jan-Ivar Bruaroey <jib@mozilla.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
- Message-ID: <57A15FAF9E58F841B2B1651FFE16D2811F1D20@GENSJZMBX03.msg.int.genesyslab.com>
Sorry, I wasn't clear. I was referring to the request for new values 'max', 'min' and 'mid', where {width: max} would mean "make it as wide as you can". "min" would ask for the minimum possible value, and 'mid' would mean "try for something in the middle of the range". We haven't introduced these yet, but there seemed to be interest in them. I think that the semantics would have to be that anything the UA chose counted as correct. Just because the property 'foo' defines its range to be 0-1000 doesn't mean that the UA can actually set a value of 1000 in every case (particularly if there are other interacting properties), so whatever the UA gives you has to count as "as good as I could do". - Jim From: Jan-Ivar Bruaroey [mailto:jib@mozilla.com] Sent: Tuesday, December 03, 2013 3:47 PM To: Jim Barnett; public-media-capture@w3.org Subject: Re: Bug 23935 - Proposal: New syntax for constraints On 11/27/13 10:55 AM, Jim Barnett wrote: I prefer the current syntax. It is more compact and makes back-off easier. Furthermore, it makes the semantics of 'best effort' values like min/max/mid easy to understand, at least in the case of optional constraints. Suppose we have optional constraints "prop1 max, prop2 max, prop3 max". This would mean: set prop1 to the largest value you can, the set prop2 to the largest value you can without changing prop1, then set prop3 to the largest value you can get without changing prop1 or prop2. The ordering of the constraints specifies the ordering of the optimizations. I don't understand your use of min and max (what is mid?) - Can you please use actual syntax? Are you saying that { width: { max: 2880 } } must return the highest value possible, up to and including 2880? If so, that doesn't match my understanding. Where in the spec do you read that? My interpretation is that there is no such guarantee, and that, given no lower bound, browsers can return anything from the lowest possible value and up to and including 2880. .: Jan-Ivar :.
Received on Tuesday, 3 December 2013 20:54:00 UTC