W3C home > Mailing lists > Public > public-css-testsuite@w3.org > January 2008

Re: CSS 2.1 tests: again (III)

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 11 Jan 2008 23:20:53 -0500
Message-ID: <47884025.2020908@inkedblade.net>
To: Gabriele Romanato <gabriele.romanato@gmail.com>
CC: css test <public-css-testsuite@w3.org>

Gabriele Romanato wrote:
> Just finished to upload the new tests:
> http://www.css-zibaldone.com/test/more/


   These four are short enough and related enough that I'd combine
   them into one test, similar to


   This looks pretty good. I've checked it in as sgml-comments-000.xht.

   I also suggest creating

     - a more advanced version that tests different valid combinations of '<!--',
       '-->' and other bits of CSS.
     - an invalid version that makes sure '<!--' and '-->' in invalid places
       causes those rules to be ignored
     - an invalid version that makes sure combinations of '<', '!', '-', '>' that
       don't form '<!--' and '-->' also cause their associated rules to be ignored.


   For both of these, you should combine the valid declaration and the invalid
   declaration into one style rule. Preferably there should be a valid declaration
   both before and after the invalid declaration. We need to make sure that only the
   invalid declaration is ignored, not the whole style rule.


   This is already covered by dbaron's test
   so I think we'll skip it.


   I'd combine these two into one test, starting with
     p {
       color: green;
       text-color: red;
       font-color: red;
   and then adding more rules that append or prepend letters and/or punctuation to
   'color', e.g.
       -color: red;
       @color: red;
       color-: red;
       color(): red;
   etc. Since "font-color" and "text-color" are rather arbitrary strings that probably
   wouldn't be in the parser, it's unlikely that a UA will fail on those. It's more likely
   that the parser doesn't know where to begin, where to stop, and/or ignores unexpected
   punctuation instead of throwing out the whole declaration.


   This is not so much a declaration parsing test as a color value parsing test. I'd
   link to
   as the primary section. Also, we don't know if a broken UA would treat #ff00 as red
   or yellow or some other color, so I'd just assert that the line is green and not
   mention red.


   Again, you want to combine these into one style rule and make sure only the invalid
   declarations are thrown out, not the whole style rule. I'd also split each error
   into its own declaration, e.g. split "color:: red !" into "color:: red;" and
   "color: red !".this


   I'd suggest splitting out the @font-face rule and turning this into a nested @media
   rule test for
   You'll need to add some valid rules inside the top-level @media rule to make sure
   they aren't ignored, that only the rules inside the nested @media rule are ignored.


   This test is incorrect. You need to swap "green" and "red".


   Great test, however I'd change it slightly to add something like
     background: red;
     border: solid green;
   (and change the description appropriately) to make sure the parser recovers after
   the unfinished string.


   This is also a great test, but I'd mark it as primarily a test for Selector grouping


   Similarly, I'd mark this as primarily a test for Descendant selectors
   Also, I'd add a few rules doing such a combination with ID selectors or the universal
   Because the punctuation ends parsing of the div's token, these are more likely to
   trigger errors than combining alphanumeric tag selectors.

Received on Saturday, 12 January 2008 04:21:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:13 UTC