- From: L. David Baron <dbaron@dbaron.org>
- Date: Wed, 28 Mar 2012 08:12:33 -0700
- To: Yves Lafon <ylafon@w3.org>
- Cc: Florian Rivoal <florianr@opera.com>, www-style@w3.org
On Wednesday 2012-03-28 10:12 -0400, Yves Lafon wrote:
> On Tue, 27 Mar 2012, Florian Rivoal wrote:
>
> >On Mon, 26 Mar 2012 18:09:42 +0200, Yves Lafon <ylafon@w3.org> wrote:
> >
> >>Also, by "and since we have multiple inter-operable
> >>implementations, it does not make much sense to change it now."
> >>Do you mean that they all pass tests containing "ratio(16
> >>/ 9)" or just that they pass "ratio(16/9)"...
> >>In the following test suite (linked form the CR doc) [2], I see
> >>only tests for "ratio(x/y)" without spaces, so I don't think
> >>that it will be hugely disruptive to do that change.
> >
> >Maybe the test suite is a bit light here, but I just checked, and all of
> >Opera and Firefox and Chrome accept the ratio with spaces in it.
>
> Yes, please add such test to the test suite so that it won't become
> an interop issue (and as I side note my parser aprse it this way as
> well)
We've had some tests for this in the test suite (though not the
exact ones you suggest) since the original version of the test
suite, in particular:
# features = [ "max-aspect-ratio", "device-aspect-ratio" ];
# for (i in features) {
# feature = features[i];
# expression_should_be_parseable(feature + ": 1/1");
# expression_should_be_parseable(feature + ": 1 /1");
# expression_should_be_parseable(feature + ": 1 / \t\n1");
# expression_should_be_parseable(feature + ": 1/\r1");
-David
--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla http://www.mozilla.org/ 𝄂
Received on Wednesday, 28 March 2012 15:13:36 UTC