Nabble - w3.org - public-css-testsuite

Re: Submission of more tests for inclusion in CSS 2.1 testsuite

2009-11-28T10:55:08Z

Hello all,

> Today, I'd like to submit a variety of new test cases:-
>
> http://test.csswg.org/source/contributors/jameshopkins/submitted/list-style-position/overflow/list-style-position-003.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/list-style-position/overflow/list-style-position-004.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/list-style-position/float/list-style-position-005.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/list-style-position/float/list-style-position-006.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/list-style-position/float/list-style-position-007.html

James,

in that
submitted/list-style-position/float/list-style-position-007.html
I suggest to replace "browser window" with "page" since the tests are
aimed at several UAs.

So,

"
To pass, there must be a circular symbol to the left of the browser
window, and a square/rectangle to the right of the browser window.
"

can be replaced with

"
To pass, there must be a circular symbol to the left of the page, and a
square/rectangle to the right of the page.
"

Also, in that test, why not just say "square"? Why say "square/rectangle"?

Also in that same test, I think

<title>CSS Test: Marker box position - adjacent sibling block box with
'float:right'</title>

should be reviewed. And it seems that such test is actually testing 2
distinct, separate expected results: marker box position and float
applied to nested child.

In all of your visibility/text-decoration tests, you have this sort of
structural markup:

<div id="test">

visible
<span>hidden</span>
</div>

I suggest to use instead:

<div>

Filler text
<span>FAILED</span>
</div>

so that the tester would know immediately that the test failed for some
reason if visibility hidden was not honored. Also, id="test" is not
needed since there is only 1 wrapping div container in all your tests.
<div id="test"> does not add any useful meaning, helpful significance to
your tests.

> http://test.csswg.org/source/contributors/jameshopkins/submitted/text-decoration/text-decoration-013.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/text-decoration/text-decoration-014.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/text-decoration/text-decoration-015.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/text-decoration/text-decoration-016.html
> http://test.csswg.org/source/contributors/jameshopkins/submitted/text-decoration/text-decoration-017.html

There are also other more "nitpicking" issues which I have emailed you
about.

best regards, Gérard
--
Contributions to the CSS 2.1 test suite:
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/

CSS 2.1 test suite (pre-alpha):
http://www.w3.org/Style/CSS/Test/CSS2.1/current/html4/

CSS 2.1 test suite contributors:
http://test.csswg.org/source/contributors/

Submission of more tests for inclusion in CSS 2.1 testsuite

2009-11-28T08:26:23Z

Submission of three tests for inclusion in CSS 2.1 testsuite

2009-11-20T14:09:09Z

I'd like to submit three test cases tonight.

Two of them test 'list-style-position' in various contexts, and the
other tests 'max-width' when used in conjunction with replaced elements.

They are available at http://idreamincode.co.uk/tests/css/w3c/testsuite-21/
(I've managed to somehow break my incoming folder)

James

Updated default attribute selector tests, 3 z-index, list-style, :focus

2009-11-12T09:34:08Z

Hello all,

Today, I updated 8 default attribute selector tests (previously
file-named attribute-selector-001 - 008), added 3 z-index tests, 1
list-style test, 1 list-style-position test, 1 focus pseudo-class test.

They are all available, reviewable at

http://test.csswg.org/source/contributors/gtalbot/submitted/

with the same date and time: 12-Nov-2009 12:02

regards, Gérard
--
Contributions to the CSS 2.1 test suite:
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/

Feedback on 2 Microsoft submitted tests on outline

2009-11-05T07:32:36Z

Hello,

There may be a problem with a few Microsoft submitted tests on outline.

Outline border is not necessarly *immediately* surrounding the border-box.
The spec unfortunately says

"
The outline may be drawn starting just outside the border edge.
"
http://www.w3.org/TR/CSS2/ui.html#dynamic-outlines

while it used to say

"
The outline is drawn starting just outside the border edge.
"
http://www.w3.org/TR/2008/REC-CSS2-20080411/ui.html#dynamic-outlines

The difference means that an user agent may have a default, arbitrary
outline-offset of "n" pixels.

This makes some tests not entirely correct or not entirely reliable, like

http://test.csswg.org/source/contributors/microsoft/submitted/Chapter_18/outline-layout-001.xht
(the complete overlapping of border-bottom: 10px solid red; is not
assured, is not certain/guaranteed)

and

the assert
<meta name="assert" content="Outline is drawn directly outside of the
border." />
in this test
http://test.csswg.org/source/contributors/microsoft/submitted/Chapter_18/outline-layout-003.xht
may not be perfectly exact, not perfectly true. Right now, the word
"directly" is somewhat questionable here. Am I nitpicking too far here?

I wish the CSS 2.1 spec would intentionally and deliberately say
"
The outline is drawn starting just outside the border edge.
"
meaning/suggesting that outline-offset is assumed to be 0 by default.

regards, Gérard

Opera 10 selectors report

2009-11-03T09:43:16Z

Hello public-css-testsuite,

Here is the implementation report for Opera 10 against the latest test suite.

Some improvements relative to the results for Opera 9.5alpha. Still missing some passes however, i think we are not quite exited CR yet unfortunately.

--
Chris Lilley mailto:chris@...
Technical Director, Interaction Domain
W3C Graphics Activity Lead
Co-Chair, W3C Hypertext CG
Selectors implementation report Opera 10.0

Selectors implementation report, Opera 10.0

Key

pass na fail crash

Test numbers in italic are failure/error tests and are likely to contain invalid CSS, yet are still quite useful for testing error handling in UAs.

Report

Opera Browser! 10.0 build 1750 Windows XP SP2 Presto/2.2.15 2009-10-28 Opera ASA Chris Lilley 2009-11-02 http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20091025/

CSS1
Selector	HTML	XML	XML w NS	XHTML
type	2 160	2 160	2 91 93 160 182	2 91 92 93 160 182
single class '.'	13 155 155a 155b 155c 155d 170b 175a 175b 175c 183			13 155 155a 155b 155c 155d 170b 171 175a 175b 175c 183
grouping ','	1 154 156 156b 156c 170 170a	1 154 156 156b 156c 170	1 154 156 156b 156c 170	1 154 156 156b 156c 170 170a
ID '#'	4 15 15b			4 15 15b 15c
descendant ' '	43 43b 181 27b	27b	27b	43 43b 181 27b
:link	16			16
:visited	17			17
:active link	19			19
:first-letter	39	39	39	39
:first-line	38	38	38	38
CSS2(.1)
Selector	HTML	XML	XML w NS	XHTML
universal '*'	3a		94 94b	3 3a 94 94b 95 96 96b
child '>'	44 44b 44c 44d 86 89	86 89	86 89	44 44b 44c 44d 86 89
multi-class '.'	14 14b 14c			14 14b 14c
:active	19b			19b
:focus	20			20
:first-child	32 170d 177b 27a	170d 177b 27a	170d 177b 27a	32 170d 177b 27a
:hover	18 18a 18b 18c	18 18b	18 18b	18 18a 18b 18c
:lang	22			22
direct sibling '+'	45 45b 45c 88 88b	88 88b	88 88b	45 45b 45c 88 88b
attribute presence '[ ]'	5	5	5 97 97b 104 104b 111 111b	5 97 97b 104 104b 111 111b
attribute equality '[ = ]'	6	6	6 98 98b 105 105b 112 112b 174a	6 98 98b 105 105b 112 112b 174a
attribute space set '[ ~= ]'	7 7b	7 7b	7 7b 99 99b 106 106b 113 113b	7 7b 99 99b 106 106b 113 113b
attribute dashed prefix '[ \|= ]'	8	8	8 100 100b 107 107b 114 114b	8 100 100b 107 107b 114 114b
:before	39a 41a	39a 41a	39a 41a	39a 41a
:after	42a	42a	42a	42a
(CSS3) Selectors
Selector	HTML	XML	XML w NS	XHTML
attribute prefix '[^=]'	9	9	9 101 101b 108 108b 115 115b	9 101 101b 108 108b 115 115b
attribute suffix '[$=]'	10	10	10 102 102b 109 109b 116 116b	10 102 102b 109 109b 116 116b
attribute substring '[*=]'	11 157 158	11 157 158	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b d3
:root	27	27	27	27
:nth-child	28 28b 27a	146a 146b 27a	146a 146b 27a	28 28b 146a 146b 27a
:nth-last-child	29 29b 27a	27a	27a	29 29b 27a
:nth-of-type	30 27a	145a 145b 27a	145a 145b 27a	30 145a 145b 27a
:nth-last-of-type	31 27a	147a 147b 27a	147a 147b 27a	31 147a 147b 27a
:last-child	33 d4 27a	27a	27a	33 d4 27a
:first-of-type	34 27a	27a	27a	34 27a
:last-of-type	35 27a	27a	27a	35 27a
:only-child	36 27a	27a	27a	36 27a
:only-of-type	37 27a	27a	27a	37 27a
:empty	148 149 149b 150 151 152	148	148	148 149 149b 150 151 152 153
:target	21 21b 21c	21b 21c	21b 21c	21 21b 21c
:enabled	23			23
:disabled	24			24
:checked	25			25
::first-letter	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a
::first-line	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a
::before	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a
::after	42 169 169a	42 169 169a	42 169 169a	42 169 169a
:not	14d 14e 54 55 56 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 144 170c 176 178 d1 d1b d5c d5e	66b 72 72b 83 144 178	66b 72 72b 83 144 174b 178	14d 14e 47 48 49 50 51 52 53 54 55 56 57 57b 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 118 119 120 121 122 123 123b 124 124b 125 125b 126 126b 127 127b 128 128b 129 129b 130 130b 131 131b 132 132b 133 133b 134 134b 135 135b 136 136b 137 137b 138 138b 139 139b 140 140b 141 141b 142 142b 143 143b 144 170c 174b 176 178 d1 d1b d5c d5e
indirect sibling '~'	46 46b 87 87b 90 90b 161 d2	87 87b 90 90b 161	87 87b 90 90b 161	46 46b 87 87b 90 90b 161 d2

Re: updated selectors implementation report template

2009-11-03T09:38:06Z

Hello public-css-testsuite,

I was about to check in the revised template from David into the W3C CVS, but noticed the following row which no longer applies:

:indeterminate d5 d5a d5d d5 d5a d5d

--
Chris Lilley mailto:chris@...
Technical Director, Interaction Domain
W3C Graphics Activity Lead
Co-Chair, W3C Hypertext CG

Review of cases from gtalbot

2009-11-03T00:22:59Z

All cases submitted by Gtalbot (http://test.csswg.org/source/contributors/gtalbot/submitted/) have been reviewed.

Issues:

The attribute selector tests (attribute-selector-001 - 008) have been identified as being ambiguous in the specs. fantasai has called this out in a recent email http://lists.w3.org/Archives/Public/www-style/2009Nov/0022.html.

All other tests conform to the guidelines and properly test the rules within the spec. At this time I am approving all the cases except for the identified attribute-selector cases.

Thanks,

Arron Eicholz

Re: Two Suggested HTML Tests for CSS2.1 Section 4.1.8 (Declarations and Properties)

2009-10-30T17:41:40Z

Tim Boland wrote:
> Attached as HTML files – comments welcome – tested so far on IE,
> Mozilla, Opera..

http://www.w3.org/2002/02/mid/2AE78383C3944F1E83BFA5C3BCE53C0D@...
http://www.w3.org/2002/02/mid/AAAE23650F934F729CB667C478090258@...

I've checked these into
http://test.csswg.org/svn/contributors/boland/
so we don't lose track of them!

~fantasai

Re: Licensing

2009-10-24T01:30:26Z

Ian Hickson wrote:

> On Fri, 23 Oct 2009, fantasai wrote:
>> Anyway. I'm having a lot of trouble with #3, because your directory
>> indexes don't include any of the support files unless they're PNG or
>> CSS. I'm getting the feeling that manually downloading all your tests is
>> not going to pick up all the requisite files--especially since I know
>> you've written tests in the past that rely on files that aren't even
>> linked from the test because they only trigger on failure cases. If you
>> can take the five minutes to zip up your adhoc/css directory from the
>> server and send them to me or to dbaron or put them up on your site
>> somewhere, that would make this a whole lot easier, and, more
>> importantly, more accurate.
>
> http://www.hixie.ch/tests/adhoc/css-2009-10-23.tar.gz

Got it. Your tests are now available via svn at
http://test.csswg.org/svn/contributors/hixie/
and should appear soon at:
http://test.csswg.org/source/contributors/hixie/

> However, this will likely not save you much time.

Judging by how long it was taking me before, it has saved me at
least a day. Thank you.

> Many of these tests are wrong, refer to other resources, depend on
> the exact directory or server structure used, etc. You're still going
> to have to go through each one by hand.

I understand. I don't have a timeframe yet, but I'll make sure the
tests get reviewed by someone familiar with the spec.

Thanks~
~fantasai

Re: Licensing

2009-10-23T20:28:59Z

On Fri, 23 Oct 2009, fantasai wrote:

>
> Anyway. I'm having a lot of trouble with #3, because your directory
> indexes don't include any of the support files unless they're PNG or
> CSS. I'm getting the feeling that manually downloading all your tests is
> not going to pick up all the requisite files--especially since I know
> you've written tests in the past that rely on files that aren't even
> linked from the test because they only trigger on failure cases. If you
> can take the five minutes to zip up your adhoc/css directory from the
> server and send them to me or to dbaron or put them up on your site
> somewhere, that would make this a whole lot easier, and, more
> importantly, more accurate.

http://www.hixie.ch/tests/adhoc/css-2009-10-23.tar.gz

However, this will likely not save you much time. Many of these tests are
wrong, refer to other resources, depend on the exact directory or server
structure used, etc. You're still going to have to go through each one by
hand.

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

4 more tests (z-index and white-space) submitted from gtalbot.org

2009-10-23T17:06:16Z

Hello all,

4 more tests to the CSS 2.1 test suite:

z-index (3 tests) and white-space (1 test)

These 4 tests are authored (authoring shared) by James Hopkins and me.

All the tests are available (in HTML 4 and XHTML 1.1), downloadable,
reviewable from

http://www.gtalbot.org/BrowserBugsSection/css21testsuite/

These 4 tests are for now in my contributor incoming folder:

http://test.csswg.org/source/contributors/gtalbot/incoming/

regards, Gérard

Re: Licensing

2009-10-23T15:32:02Z

Ian Hickson wrote:

> On Wed, 21 Oct 2009, fantasai wrote:
>> Ian Hickson wrote:
>>> On Wed, 21 Oct 2009, fantasai wrote:
>>>> I'd like to get these tests checked in this week, so we can get an
>>>> accurate build of the test coverage report for TPAC. There's three ways
>>>> this could happen:
>>>>
>>>> 1. I give you access to check in the tests yourself.
>>>> 2. You send me a tarball of the tests and associated files.
>>>> 3. I scrape them off your website.
>>>>
>>>> All three methods work for me, although if any server-side configuration
>>>> is required #1 or #2 is definitely the best way to go.
>>> I won't have time to do #1 or #3 for a long time.
>> #3 doesn't require any work on your part, other than replying
>> and saying that this is what you want me to do. So I don't
>> understand your answer.
>
> Sorry, I meant #1 and #2. I've already said #3 is fine?:
>
> http://lists.w3.org/Archives/Public/public-css-testsuite/2009Oct/0009.html

You said it was fine but implied that I shouldn't be doing it because
you wanted dbaron to do something.

Anyway. I'm having a lot of trouble with #3, because your directory
indexes don't include any of the support files unless they're PNG
or CSS. I'm getting the feeling that manually downloading all your
tests is not going to pick up all the requisite files--especially
since I know you've written tests in the past that rely on files that
aren't even linked from the test because they only trigger on failure
cases. If you can take the five minutes to zip up your adhoc/css
directory from the server and send them to me or to dbaron or put them
up on your site somewhere, that would make this a whole lot easier, and,
more importantly, more accurate.

~fantasai

Re: Licensing

2009-10-22T01:37:01Z

On Wed, 21 Oct 2009, fantasai wrote:

> Ian Hickson wrote:
> > On Wed, 21 Oct 2009, fantasai wrote:
> > > I'd like to get these tests checked in this week, so we can get an
> > > accurate build of the test coverage report for TPAC. There's three ways
> > > this could happen:
> > >
> > > 1. I give you access to check in the tests yourself.
> > > 2. You send me a tarball of the tests and associated files.
> > > 3. I scrape them off your website.
> > >
> > > All three methods work for me, although if any server-side configuration
> > > is required #1 or #2 is definitely the best way to go.
> >
> > I won't have time to do #1 or #3 for a long time.
>
> #3 doesn't require any work on your part, other than replying
> and saying that this is what you want me to do. So I don't
> understand your answer.

Sorry, I meant #1 and #2. I've already said #3 is fine?:

http://lists.w3.org/Archives/Public/public-css-testsuite/2009Oct/0009.html

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

Re: Licensing

2009-10-21T17:41:02Z

Ian Hickson wrote:

> On Wed, 21 Oct 2009, fantasai wrote:
>> I'd like to get these tests checked in this week, so we can get an
>> accurate build of the test coverage report for TPAC. There's three ways
>> this could happen:
>>
>> 1. I give you access to check in the tests yourself.
>> 2. You send me a tarball of the tests and associated files.
>> 3. I scrape them off your website.
>>
>> All three methods work for me, although if any server-side configuration
>> is required #1 or #2 is definitely the best way to go.
>
> I won't have time to do #1 or #3 for a long time.

#3 doesn't require any work on your part, other than replying
and saying that this is what you want me to do. So I don't
understand your answer.

~fantasai

Re: Licensing

2009-10-21T16:12:32Z

On Wed, 21 Oct 2009, fantasai wrote:

>
> I'd like to get these tests checked in this week, so we can get an
> accurate build of the test coverage report for TPAC. There's three ways
> this could happen:
>
> 1. I give you access to check in the tests yourself.
> 2. You send me a tarball of the tests and associated files.
> 3. I scrape them off your website.
>
> All three methods work for me, although if any server-side configuration
> is required #1 or #2 is definitely the best way to go.

I won't have time to do #1 or #3 for a long time.

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

Re: Licensing

2009-10-21T14:32:40Z

Ian Hickson wrote:

> On Mon, 19 Oct 2009, fantasai wrote:
>> Ian Hickson wrote:
>>> You still misunderstand; my point is that I am not willing to license
>>> my tests under _any_ license unless the W3C commits to using one of
>>> those three licenses for the entirety of the CSS 2.1 test suite and
>>> indeed all other CSS test suites, just like the HTML working group has
>>> committed to using the MIT license for their test suite.
>> I might've asked this already, but... Is the W3C Test Suite / BSD dual
>> license acceptable to you?
>> http://www.w3.org/Consortium/Legal/2008/04-testsuite-copyright (The
>> restrictions on using the tests under BSD are under trademark law, not
>> copyright law: the code is under standard BSD, W3C is just asserting
>> control over use of its own trademark in association with the tests.)
>>
>> If that works for you, I'd like to have your CSS tests checked into
>> test.csswg.org SVN. I can give you an account there, or I can do it for
>> you: your choice.
>
> I believe dbaron has the ball on this issue; he and I discussed this topic
> recently.

It seems dbaron doesn't consider himself on the ball on this issue.

I'd like to get these tests checked in this week, so we can get an
accurate build of the test coverage report for TPAC. There's three
ways this could happen:

1. I give you access to check in the tests yourself.
2. You send me a tarball of the tests and associated files.
3. I scrape them off your website.

All three methods work for me, although if any server-side configuration
is required #1 or #2 is definitely the best way to go.

Please let me know what you prefer.

Thanks~
~fantasai

Re: selectors implementation report template, again

2009-10-21T10:58:33Z

Oops. In both the template and the Firefox implementation report I
forgot to undo making the style sheet link absolute. In both cases,
when they're checked in, this:
<link type="text/css" rel="stylesheet" href="http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/implementationreport.css" />
should be changed to this:
<link type="text/css" rel="stylesheet" href="implementationreport.css" />
or (if the latter is already there) removed.

-David

--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/

selectors implementation report for Firefox 3.5

2009-10-21T10:55:59Z

Here is the revised selectors implementation report for Firefox 3.5,
per the template revisions in my previous message.

In this report, there is only a single test not marked as passing:
http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20090603/xhtml/tests/css3-modsel-15c.xml
and I marked it as 'N/A' because:
"This test requires support for two or more of XHTML, xml:id, and
DOM3 Core."

-David

--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/

Selectors implementation report for Firefox 3.5.3

Selectors implementation report for Firefox 3.5.3

Key

pass na fail crash

Test numbers in italic are failure/error tests and are likely to contain invalid CSS, yet are still quite useful for testing error handling in UAs.

Report

hyperlinked name of user agent Firefox 3.5.3 Linux Gecko 2009-09-09 Mozilla Corporation L. David Baron 2009-10-21 http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20090603/

CSS1
Selector	HTML	XML	XML w NS	XHTML
type	2 160	2 160	2 91 93 160 182	2 91 92 93 160 182
single class '.'	13 155 155a 155b 155c 155d 170b 175a 175b 175c 183			13 155 155a 155b 155c 155d 170b 171 175a 175b 175c 183
grouping ','	1 154 156 156b 156c 170 170a	1 154 156 156b 156c 170	1 154 156 156b 156c 170	1 154 156 156b 156c 170 170a
ID '#'	4 15 15b			4 15 15b 15c
descendant ' '	43 43b 181 27b	27b	27b	43 43b 181 27b
:link	16			16
:visited	17			17
:active link	19			19
:first-letter	39	39	39	39
:first-line	38	38	38	38
CSS2(.1)
Selector	HTML	XML	XML w NS	XHTML
universal '*'	3a		94 94b	3 3a 94 94b 95 96 96b
child '>'	44 44b 44c 44d 86 89	86 89	86 89	44 44b 44c 44d 86 89
multi-class '.'	14 14b 14c			14 14b 14c
:active	19b			19b
:focus	20			20
:first-child	32 170d 177b 27a	170d 177b 27a	170d 177b 27a	32 170d 177b 27a
:hover	18 18a 18b 18c	18 18b	18 18b	18 18a 18b 18c
:lang	22			22
direct sibling '+'	45 45b 45c 88 88b	88 88b	88 88b	45 45b 45c 88 88b
attribute presence '[ ]'	5	5	5 97 97b 104 104b 111 111b	5 97 97b 104 104b 111 111b
attribute equality '[ = ]'	6	6	6 98 98b 105 105b 112 112b 174a	6 98 98b 105 105b 112 112b 174a
attribute space set '[ ~= ]'	7 7b	7 7b	7 7b 99 99b 106 106b 113 113b	7 7b 99 99b 106 106b 113 113b
attribute dashed prefix '[ \|= ]'	8	8	8 100 100b 107 107b 114 114b	8 100 100b 107 107b 114 114b
:before	39a 41a	39a 41a	39a 41a	39a 41a
:after	42a	42a	42a	42a
(CSS3) Selectors
Selector	HTML	XML	XML w NS	XHTML
attribute prefix '[^=]'	9 184b	9 184b	9 101 101b 108 108b 115 115b 184b	9 101 101b 108 108b 115 115b 184b
attribute suffix '[$=]'	10 184a	10 184a	10 102 102b 109 109b 116 116b 184a	10 102 102b 109 109b 116 116b 184a
attribute substring '[*=]'	11 157 158 184c	11 157 158 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b d3 184c
:root	27	27	27	27
:nth-child	28 28b 27a	146a 146b 27a	146a 146b 27a	28 28b 146a 146b 27a
:nth-last-child	29 29b 27a	27a	27a	29 29b 27a
:nth-of-type	30 27a	145a 145b 27a	145a 145b 27a	30 145a 145b 27a
:nth-last-of-type	31 27a	147a 147b 27a	147a 147b 27a	31 147a 147b 27a
:last-child	33 d4 27a	27a	27a	33 d4 27a
:first-of-type	34 27a	27a	27a	34 27a
:last-of-type	35 27a	27a	27a	35 27a
:only-child	36 27a	27a	27a	36 27a
:only-of-type	37 27a	27a	27a	37 27a
:empty	148 149 149b 150 151 152	148	148	148 149 149b 150 151 152 153
:target	21 21b 21c	21b 21c	21b 21c	21 21b 21c
:enabled	23			23
:disabled	24			24
:checked	25			25
::first-letter	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a
::first-line	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a
::before	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a
::after	42 169 169a	42 169 169a	42 169 169a	42 169 169a
:not	14d 14e 54 55 56 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 144 170c 176 178 184d 184e 184f d1 d1b	66b 72 72b 83 144 178 184d 184e 184f	66b 72 72b 83 144 174b 178 184d 184e 184f	14d 14e 47 48 49 50 51 52 53 54 55 56 57 57b 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 118 119 120 121 122 123 123b 124 124b 125 125b 126 126b 127 127b 128 128b 129 129b 130 130b 131 131b 132 132b 133 133b 134 134b 135 135b 136 136b 137 137b 138 138b 139 139b 140 140b 141 141b 142 142b 143 143b 144 170c 174b 176 178 184d 184e 184f d1 d1b
indirect sibling '~'	46 46b 87 87b 90 90b 161 d2	87 87b 90 90b 161	87 87b 90 90b 161	46 46b 87 87b 90 90b 161 d2

selectors implementation report template, again

2009-10-21T10:51:00Z

Here is the selectors implementation report template, revised yet
again (relative to my email a few minutes ago).

The revisions from the previous one I sent are:

* commented out all :indeterminate tests (modsel-d5*) because
:indeterminate has been dropped from the spec

* fixed broken links to modsel-184* in all columns other than the
HTML column

* fixed duplication of modsel-184{d,e,f} in the third column

-David

--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/

Selectors implementation report TEMPLATE

Selectors implementation report TEMPLATE

Key

pass na fail crash

Test numbers in italic are failure/error tests and are likely to contain invalid CSS, yet are still quite useful for testing error handling in UAs.

Report

hyperlinked name of user agent version x.y.z platform/OS the rendering engine used in the UA date user agent was shipped hyperlinked implementor/company report writer date report written http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20090603/

CSS1
Selector	HTML	XML	XML w NS	XHTML
type	2 160	2 160	2 91 93 160 182	2 91 92 93 160 182
single class '.'	13 155 155a 155b 155c 155d 170b 175a 175b 175c 183			13 155 155a 155b 155c 155d 170b 171 175a 175b 175c 183
grouping ','	1 154 156 156b 156c 170 170a	1 154 156 156b 156c 170	1 154 156 156b 156c 170	1 154 156 156b 156c 170 170a
ID '#'	4 15 15b			4 15 15b 15c
descendant ' '	43 43b 181 27b	27b	27b	43 43b 181 27b
:link	16			16
:visited	17			17
:active link	19			19
:first-letter	39	39	39	39
:first-line	38	38	38	38
CSS2(.1)
Selector	HTML	XML	XML w NS	XHTML
universal '*'	3a		94 94b	3 3a 94 94b 95 96 96b
child '>'	44 44b 44c 44d 86 89	86 89	86 89	44 44b 44c 44d 86 89
multi-class '.'	14 14b 14c			14 14b 14c
:active	19b			19b
:focus	20			20
:first-child	32 170d 177b 27a	170d 177b 27a	170d 177b 27a	32 170d 177b 27a
:hover	18 18a 18b 18c	18 18b	18 18b	18 18a 18b 18c
:lang	22			22
direct sibling '+'	45 45b 45c 88 88b	88 88b	88 88b	45 45b 45c 88 88b
attribute presence '[ ]'	5	5	5 97 97b 104 104b 111 111b	5 97 97b 104 104b 111 111b
attribute equality '[ = ]'	6	6	6 98 98b 105 105b 112 112b 174a	6 98 98b 105 105b 112 112b 174a
attribute space set '[ ~= ]'	7 7b	7 7b	7 7b 99 99b 106 106b 113 113b	7 7b 99 99b 106 106b 113 113b
attribute dashed prefix '[ \|= ]'	8	8	8 100 100b 107 107b 114 114b	8 100 100b 107 107b 114 114b
:before	39a 41a	39a 41a	39a 41a	39a 41a
:after	42a	42a	42a	42a
(CSS3) Selectors
Selector	HTML	XML	XML w NS	XHTML
attribute prefix '[^=]'	9 184b	9 184b	9 101 101b 108 108b 115 115b 184b	9 101 101b 108 108b 115 115b 184b
attribute suffix '[$=]'	10 184a	10 184a	10 102 102b 109 109b 116 116b 184a	10 102 102b 109 109b 116 116b 184a
attribute substring '[*=]'	11 157 158 184c	11 157 158 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b d3 184c
:root	27	27	27	27
:nth-child	28 28b 27a	146a 146b 27a	146a 146b 27a	28 28b 146a 146b 27a
:nth-last-child	29 29b 27a	27a	27a	29 29b 27a
:nth-of-type	30 27a	145a 145b 27a	145a 145b 27a	30 145a 145b 27a
:nth-last-of-type	31 27a	147a 147b 27a	147a 147b 27a	31 147a 147b 27a
:last-child	33 d4 27a	27a	27a	33 d4 27a
:first-of-type	34 27a	27a	27a	34 27a
:last-of-type	35 27a	27a	27a	35 27a
:only-child	36 27a	27a	27a	36 27a
:only-of-type	37 27a	27a	27a	37 27a
:empty	148 149 149b 150 151 152	148	148	148 149 149b 150 151 152 153
:target	21 21b 21c	21b 21c	21b 21c	21 21b 21c
:enabled	23			23
:disabled	24			24
:checked	25			25
::first-letter	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a
::first-line	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a
::before	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a
::after	42 169 169a	42 169 169a	42 169 169a	42 169 169a
:not	14d 14e 54 55 56 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 144 170c 176 178 184d 184e 184f d1 d1b	66b 72 72b 83 144 178 184d 184e 184f	66b 72 72b 83 144 174b 178 184d 184e 184f	14d 14e 47 48 49 50 51 52 53 54 55 56 57 57b 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 118 119 120 121 122 123 123b 124 124b 125 125b 126 126b 127 127b 128 128b 129 129b 130 130b 131 131b 132 132b 133 133b 134 134b 135 135b 136 136b 137 137b 138 138b 139 139b 140 140b 141 141b 142 142b 143 143b 144 170c 174b 176 178 184d 184e 184f d1 d1b
indirect sibling '~'	46 46b 87 87b 90 90b 161 d2	87 87b 90 90b 161	87 87b 90 90b 161	46 46b 87 87b 90 90b 161 d2

Firefox 3.5.3 selectors implementation report

2009-10-21T10:35:02Z

I followed all of the test links in the report template I sent a few
minutes ago, and filled it out for Firefox 3.5. Here is the result.

However, I think the report template needs some additional
corrections. I'll send an updated template and then an updated
report in a bit.

-David

--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/

Selectors implementation report for Firefox 3.5.3

Selectors implementation report for Firefox 3.5.3

Key

pass na fail crash

Test numbers in italic are failure/error tests and are likely to contain invalid CSS, yet are still quite useful for testing error handling in UAs.

Report

hyperlinked name of user agent Firefox 3.5.3 Linux Gecko 2009-09-09 Mozilla Corporation L. David Baron 2009-10-21 http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20090603/

CSS1
Selector	HTML	XML	XML w NS	XHTML
type	2 160	2 160	2 91 93 160 182	2 91 92 93 160 182
single class '.'	13 155 155a 155b 155c 155d 170b 175a 175b 175c 183			13 155 155a 155b 155c 155d 170b 171 175a 175b 175c 183
grouping ','	1 154 156 156b 156c 170 170a	1 154 156 156b 156c 170	1 154 156 156b 156c 170	1 154 156 156b 156c 170 170a
ID '#'	4 15 15b			4 15 15b 15c
descendant ' '	43 43b 181 27b	27b	27b	43 43b 181 27b
:link	16			16
:visited	17			17
:active link	19			19
:first-letter	39	39	39	39
:first-line	38	38	38	38
CSS2(.1)
Selector	HTML	XML	XML w NS	XHTML
universal '*'	3a		94 94b	3 3a 94 94b 95 96 96b
child '>'	44 44b 44c 44d 86 89	86 89	86 89	44 44b 44c 44d 86 89
multi-class '.'	14 14b 14c			14 14b 14c
:active	19b			19b
:focus	20			20
:first-child	32 170d 177b 27a	170d 177b 27a	170d 177b 27a	32 170d 177b 27a
:hover	18 18a 18b 18c	18 18b	18 18b	18 18a 18b 18c
:lang	22			22
direct sibling '+'	45 45b 45c 88 88b	88 88b	88 88b	45 45b 45c 88 88b
attribute presence '[ ]'	5	5	5 97 97b 104 104b 111 111b	5 97 97b 104 104b 111 111b
attribute equality '[ = ]'	6	6	6 98 98b 105 105b 112 112b 174a	6 98 98b 105 105b 112 112b 174a
attribute space set '[ ~= ]'	7 7b	7 7b	7 7b 99 99b 106 106b 113 113b	7 7b 99 99b 106 106b 113 113b
attribute dashed prefix '[ \|= ]'	8	8	8 100 100b 107 107b 114 114b	8 100 100b 107 107b 114 114b
:before	39a 41a	39a 41a	39a 41a	39a 41a
:after	42a	42a	42a	42a
(CSS3) Selectors
Selector	HTML	XML	XML w NS	XHTML
attribute prefix '[^=]'	9 184b	9 184b	9 101 101b 108 108b 115 115b 184b	9 101 101b 108 108b 115 115b 184b
attribute suffix '[$=]'	10 184a	10 184a	10 102 102b 109 109b 116 116b 184a	10 102 102b 109 109b 116 116b 184a
attribute substring '[*=]'	11 157 158 184c	11 157 158 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b d3 184c
:root	27	27	27	27
:nth-child	28 28b 27a	146a 146b 27a	146a 146b 27a	28 28b 146a 146b 27a
:nth-last-child	29 29b 27a	27a	27a	29 29b 27a
:nth-of-type	30 27a	145a 145b 27a	145a 145b 27a	30 145a 145b 27a
:nth-last-of-type	31 27a	147a 147b 27a	147a 147b 27a	31 147a 147b 27a
:last-child	33 d4 27a	27a	27a	33 d4 27a
:first-of-type	34 27a	27a	27a	34 27a
:last-of-type	35 27a	27a	27a	35 27a
:only-child	36 27a	27a	27a	36 27a
:only-of-type	37 27a	27a	27a	37 27a
:empty	148 149 149b 150 151 152	148	148	148 149 149b 150 151 152 153
:target	21 21b 21c	21b 21c	21b 21c	21 21b 21c
:enabled	23			23
:disabled	24			24
:checked	25			25
:indeterminate	d5 d5a d5d			d5 d5a d5d
::first-letter	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a
::first-line	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a
::before	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a
::after	42 169 169a	42 169 169a	42 169 169a	42 169 169a
:not	14d 14e 54 55 56 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 144 170c 176 178 184d 184e 184f d1 d1b d5b d5c d5e	66b 72 72b 83 144 178 184d 184e 184f	66b 72 72b 83 144 174b 178 184d 184e 184f 184d 184e 184f	14d 14e 47 48 49 50 51 52 53 54 55 56 57 57b 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 118 119 120 121 122 123 123b 124 124b 125 125b 126 126b 127 127b 128 128b 129 129b 130 130b 131 131b 132 132b 133 133b 134 134b 135 135b 136 136b 137 137b 138 138b 139 139b 140 140b 141 141b 142 142b 143 143b 144 170c 174b 176 178 184d 184e 184f d1 d1b d5b d5c d5e
indirect sibling '~'	46 46b 87 87b 90 90b 161 d2	87 87b 90 90b 161	87 87b 90 90b 161	46 46b 87 87b 90 90b 161 d2

updated selectors implementation report template

2009-10-21T10:05:08Z

Here is a revised version of
http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/implementreportTEMPLATE.html

It has the following four corrections:

* the default to lang="tr" has been removed from the name of the
author of the report

* the links to tests have all been updated to point to the 20090603
test suite (instead of 20060307)

* the links to tests that are not commented out now all have
class='f' (some were previously missing class attributes)

* the links to tests that are commented out now all have
class='na' (some were previously missing class attributes, and
most were previously class='f', although some were previously
class='na')

-David

--
L. David Baron http://dbaron.org/
Mozilla Corporation http://www.mozilla.com/

Selectors implementation report TEMPLATE

Selectors implementation report TEMPLATE

Key

pass na fail crash

Test numbers in italic are failure/error tests and are likely to contain invalid CSS, yet are still quite useful for testing error handling in UAs.

Report

CSS1
Selector	HTML	XML	XML w NS	XHTML
type	2 160	2 160	2 91 93 160 182	2 91 92 93 160 182
single class '.'	13 155 155a 155b 155c 155d 170b 175a 175b 175c 183			13 155 155a 155b 155c 155d 170b 171 175a 175b 175c 183
grouping ','	1 154 156 156b 156c 170 170a	1 154 156 156b 156c 170	1 154 156 156b 156c 170	1 154 156 156b 156c 170 170a
ID '#'	4 15 15b			4 15 15b 15c
descendant ' '	43 43b 181 27b	27b	27b	43 43b 181 27b
:link	16			16
:visited	17			17
:active link	19			19
:first-letter	39	39	39	39
:first-line	38	38	38	38
CSS2(.1)
Selector	HTML	XML	XML w NS	XHTML
universal '*'	3a		94 94b	3 3a 94 94b 95 96 96b
child '>'	44 44b 44c 44d 86 89	86 89	86 89	44 44b 44c 44d 86 89
multi-class '.'	14 14b 14c			14 14b 14c
:active	19b			19b
:focus	20			20
:first-child	32 170d 177b 27a	170d 177b 27a	170d 177b 27a	32 170d 177b 27a
:hover	18 18a 18b 18c	18 18b	18 18b	18 18a 18b 18c
:lang	22			22
direct sibling '+'	45 45b 45c 88 88b	88 88b	88 88b	45 45b 45c 88 88b
attribute presence '[ ]'	5	5	5 97 97b 104 104b 111 111b	5 97 97b 104 104b 111 111b
attribute equality '[ = ]'	6	6	6 98 98b 105 105b 112 112b 174a	6 98 98b 105 105b 112 112b 174a
attribute space set '[ ~= ]'	7 7b	7 7b	7 7b 99 99b 106 106b 113 113b	7 7b 99 99b 106 106b 113 113b
attribute dashed prefix '[ \|= ]'	8	8	8 100 100b 107 107b 114 114b	8 100 100b 107 107b 114 114b
:before	39a 41a	39a 41a	39a 41a	39a 41a
:after	42a	42a	42a	42a
(CSS3) Selectors
Selector	HTML	XML	XML w NS	XHTML
attribute prefix '[^=]'	9 184b	9 184b	9 101 101b 108 108b 115 115b 184b	9 101 101b 108 108b 115 115b 184b
attribute suffix '[$=]'	10 184a	10 184a	10 102 102b 109 109b 116 116b 184a	10 102 102b 109 109b 116 116b 184a
attribute substring '[*=]'	11 157 158 184c	11 157 158 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b 184c	11 103 103b 110 110b 117 117b 157 158 172a 172b 173a 173b d3 184c
:root	27	27	27	27
:nth-child	28 28b 27a	146a 146b 27a	146a 146b 27a	28 28b 146a 146b 27a
:nth-last-child	29 29b 27a	27a	27a	29 29b 27a
:nth-of-type	30 27a	145a 145b 27a	145a 145b 27a	30 145a 145b 27a
:nth-last-of-type	31 27a	147a 147b 27a	147a 147b 27a	31 147a 147b 27a
:last-child	33 d4 27a	27a	27a	33 d4 27a
:first-of-type	34 27a	27a	27a	34 27a
:last-of-type	35 27a	27a	27a	35 27a
:only-child	36 27a	27a	27a	36 27a
:only-of-type	37 27a	27a	27a	37 27a
:empty	148 149 149b 150 151 152	148	148	148 149 149b 150 151 152 153
:target	21 21b 21c	21b 21c	21b 21c	21 21b 21c
:enabled	23			23
:disabled	24			24
:checked	25			25
:indeterminate	d5 d5a d5d			d5 d5a d5d
::first-letter	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a	39b 166 166a 180a
::first-line	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a	167 167a 179 179a
::before	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a	39c 41 168 168a
::after	42 169 169a	42 169 169a	42 169 169a	42 169 169a
:not	14d 14e 54 55 56 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 144 170c 176 178 184d 184e 184f d1 d1b d5b d5c d5e	66b 72 72b 83 144 178 184d 184e 184f	66b 72 72b 83 144 174b 178 184d 184e 184f 184d 184e 184f	14d 14e 47 48 49 50 51 52 53 54 55 56 57 57b 59 60 61 62 63 64 65 66 66b 67 68 69 70 72 72b 73 73b 74 74b 75 75b 76 76b 77 77b 78 78b 79 80 81 81b 82 82b 83 118 119 120 121 122 123 123b 124 124b 125 125b 126 126b 127 127b 128 128b 129 129b 130 130b 131 131b 132 132b 133 133b 134 134b 135 135b 136 136b 137 137b 138 138b 139 139b 140 140b 141 141b 142 142b 143 143b 144 170c 174b 176 178 184d 184e 184f d1 d1b d5b d5c d5e
indirect sibling '~'	46 46b 87 87b 90 90b 161 d2	87 87b 90 90b 161	87 87b 90 90b 161	46 46b 87 87b 90 90b 161 d2

Re: Licensing

2009-10-19T16:20:26Z

On Mon, 19 Oct 2009, fantasai wrote:
>
> I might've asked this already, but... Is the W3C Test Suite / BSD dual
> license acceptable to you?
> http://www.w3.org/Consortium/Legal/2008/04-testsuite-copyright

I am ok with the tests at http://www.hixie.ch/tests/ being used under the
above license.

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

Re: Licensing

2009-10-19T15:31:55Z

On Mon, 19 Oct 2009, fantasai wrote:

> Ian Hickson wrote:
> >
> > You still misunderstand; my point is that I am not willing to license
> > my tests under _any_ license unless the W3C commits to using one of
> > those three licenses for the entirety of the CSS 2.1 test suite and
> > indeed all other CSS test suites, just like the HTML working group has
> > committed to using the MIT license for their test suite.
>
> I might've asked this already, but... Is the W3C Test Suite / BSD dual
> license acceptable to you?
> http://www.w3.org/Consortium/Legal/2008/04-testsuite-copyright (The
> restrictions on using the tests under BSD are under trademark law, not
> copyright law: the code is under standard BSD, W3C is just asserting
> control over use of its own trademark in association with the tests.)
>
> If that works for you, I'd like to have your CSS tests checked into
> test.csswg.org SVN. I can give you an account there, or I can do it for
> you: your choice.

I believe dbaron has the ball on this issue; he and I discussed this topic
recently.

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

Re: Licensing

2009-10-19T14:41:23Z

Ian Hickson wrote:
>
> You still misunderstand; my point is that I am not willing to license my
> tests under _any_ license unless the W3C commits to using one of those
> three licenses for the entirety of the CSS 2.1 test suite and indeed all
> other CSS test suites, just like the HTML working group has committed to
> using the MIT license for their test suite.

I might've asked this already, but... Is the W3C Test Suite / BSD dual
license acceptable to you?
http://www.w3.org/Consortium/Legal/2008/04-testsuite-copyright
(The restrictions on using the tests under BSD are under trademark law,
not copyright law: the code is under standard BSD, W3C is just asserting
control over use of its own trademark in association with the tests.)

If that works for you, I'd like to have your CSS tests checked into
test.csswg.org SVN. I can give you an account there, or I can do it for
you: your choice.

~fantasai

Re: Advice sought about combining css testing with databasing of code variables

2009-10-19T14:23:32Z

> David Southwell wrote:
> > Hi
> >
> > This is my first posting to this list which I joined for the following
> > reasons.
> >
> > 1. I understand that those with substantial experience of css can be
> > found here.
> > 2. The focus of the list is upon css testing.
> > 3. I am thinking of embarking upon a project which
> > (a) needs to validate existing css code and having done so
> > (b) can then extract css code variables, the snippet of code that
> > contains each variable and then index the variables and the snippets and
> > store the extracted data in a mysql database.
> > 4. I am in serious need of advice and guidance about tools that could
> > help me achieve these goals.
> >
> > It occurs to me that any tool capable of parsing css may also be capable
> > of extracting snippets and identifying variables. The question for me is
> > what tools might provide a good starting point.
> >
> > May I thank you in advance for your replies
>
> CSS doesn't have variables currently, so I'm not sure what you're trying to
> do.
>
> ~fantasai
>

Sorry

I should have used the term value.

e.g. a color code is a value which really needs to be a variable!!! So I
suppose I am trying to find a way around the variables limitation of css which
IMHO is its greatest weakness.

What I want to do is to use a parser to identify "values" in a css file.
Replace those values witha placeholder e.g $my_color to generate an enhanced
.css file [.ecss] . Then create a ecss file configuration utility which
enables an adminstrator to write
$my_color = "red"
in a configuration file Subsequentlt a .css file is generated by repplacing
the placeholders with the desired value from the configuration file.

David

Re: Advice sought about combining css testing with databasing of code variables

2009-10-19T12:44:32Z

David Southwell wrote:

> Hi
>
> This is my first posting to this list which I joined for the following
> reasons.
>
> 1. I understand that those with substantial experience of css can be found
> here.
> 2. The focus of the list is upon css testing.
> 3. I am thinking of embarking upon a project which
> (a) needs to validate existing css code and having done so
> (b) can then extract css code variables, the snippet of code that contains
> each variable and then index the variables and the snippets and store the
> extracted data in a mysql database.
> 4. I am in serious need of advice and guidance about tools that could help me
> achieve these goals.
>
> It occurs to me that any tool capable of parsing css may also be capable of
> extracting snippets and identifying variables. The question for me is what
> tools might provide a good starting point.
>
> May I thank you in advance for your replies

CSS doesn't have variables currently, so I'm not sure what you're trying to do.

~fantasai

Advice sought about combining css testing with databasing of code variables

2009-10-19T05:53:57Z

Hi

This is my first posting to this list which I joined for the following
reasons.

1. I understand that those with substantial experience of css can be found
here.
2. The focus of the list is upon css testing.
3. I am thinking of embarking upon a project which
(a) needs to validate existing css code and having done so
(b) can then extract css code variables, the snippet of code that contains
each variable and then index the variables and the snippets and store the
extracted data in a mysql database.
4. I am in serious need of advice and guidance about tools that could help me
achieve these goals.

It occurs to me that any tool capable of parsing css may also be capable of
extracting snippets and identifying variables. The question for me is what
tools might provide a good starting point.

May I thank you in advance for your replies

David Southwell

microsoft/first-line-selector-011.xht

2009-10-12T14:40:45Z

http://test.csswg.org/source/contributors/microsoft/submitted/Chapter_5/first-line-selector-011.xht

This test doesn't seem quite right. Try relative positioning
the span with position: relative; left: 10em; top: 3em; and
you'll see what's happening: the green background is being
applied to either the line box itself or the anonymous inline
around the inline block, not to the inline-block. The test
should be changed to reflect this model somehow, otherwise
we'll have implementors trying to pass it by doing something
stupid.

I'd suggest testing the assertion given in the meta tag with
div:first-line { color: red; } and asserting for no red. Even
better would be something like this:

<style>
span { display: inline-block; }
div { background: white; color: white; }
div:first-line { color: red; font-weight: bold; }
</style>

<div><span>FAIL<br/>FAIL</span></div>

~fantasai

Re: [Selectors] Clarify when universal selector may be omitted

2009-09-29T17:06:51Z

Boris Zbarsky On 09-09-30 00.32:

> On 9/29/09 1:58 PM, Leif Halvard Silli wrote:
>> Here is a text proposal:
>>
>> "If the universal selector is not the only component of a sequence of
>> simple selectors and if it also is without the namespace component, then
>> the universal selector may be omitted."
>
> This sounds fine to me, though not strictly necessary. The "universal
> selector" is not '*' in Selectors but "an optional namespace component
> followed by '*'".

And that is why I said "and if it [the universal selector] is
without the namespace component". The draft: "an optional
namespace component is now allowed in element type selectors, the
universal selector and attribute selectors".[*] Given the selector
sequence 'dc|*[attr]', then dropping the universal selector (dc|*)
would be risky. What is the not strictly necessary that I said?

> Which means that while you can omit the whole thing,
> you can't just omit the '*' and include the namespace component,
> Webkit's behavior to the contrary notwithstanding.

What seems strictly necessary is to better the CSS 3 Selectors
text which, by quoting CSS21, is focusing on the "*" character:

"If the universal selector is not the only component of a sequence
of simple selectors, the * may be omitted."

That appears tautological and only means you can't drop the '*'
here: *{}. With a kind reading, it also means that you can't drop
the second '*' here: *|*{}. If you do not have enough baggage,
then it means that you can drop the second "*" here: *|*{}. If you
have too much CSS 21 baggage then it means that you can drop the
second '*' here: *|*[attr].

Now, you formulated the question: when can we drop the
universal selector? However, perhaps the question that CSS 3
Selectors tries to answer in that sentence is when we can drop the
'*'? (Which is when dropping is guaranteed to not affect the
selection.) If so, then the text could be reformulated e.g. like this:

"When the * character is the only component of the universal
selector, except when the universal selector is the only simple
selector in the sequence, then the universal selector may be
omitted from the simple selectors sequence.

[*] The draft speaks of the namespace component as an optional
component of the simple selectors components: a component of a
component. http://www.w3.org/TR/css3-selectors/#changesFromCSS2
--
leif halvard silli

Re: [Selectors] Clarify when universal selector may be omitted (was: [CSSWG] Release Candidate for CSS Namespaces Test Suite)

2009-09-29T15:32:05Z

On 9/29/09 1:58 PM, Leif Halvard Silli wrote:
> Here is a text proposal:
>
> "If the universal selector is not the only component of a sequence of
> simple selectors and if it also is without the namespace component, then
> the universal selector may be omitted."

This sounds fine to me, though not strictly necessary. The "universal
selector" is not '*' in Selectors but "an optional namespace component
followed by '*'". Which means that while you can omit the whole thing,
you can't just omit the '*' and include the namespace component,
Webkit's behavior to the contrary notwithstanding.

-Boris

Re: [CSSWG] Release Candidate for CSS Namespaces Test Suite

2009-09-29T11:25:20Z

Anne van Kesteren On 09-09-29 18.07:

> On Tue, 29 Sep 2009 17:57:22 +0200, Leif Halvard Silli
>> Anne van Kesteren On 09-09-29 15.24:

>> This focus on the character '*' makes it seem as if there is a shorthand
>> for the universal selector - namely to drop it.
>
> The specification could be clearer I suppose.

1+

[...]

>>> No, that is reading between the lines. (And contrary to the grammar.)
>>> Your further examples seem all along the same lines of not reading
>>> the specification literally and trying to infer things that are not
>>> there.
>> It is not reading between the line, it is reading while being inspired
>> by CSS21.
>
> That is called reading between the lines.

It is called something else. But the interesting thing is whether
the draft is literal enough or if it "could be clearer".
--
leif halvard silli

Re: [CSSWG] Release Candidate for CSS Namespaces Test Suite

2009-09-29T10:58:46Z

Boris Zbarsky On 09-09-29 18.02:

> On 9/29/09 11:57 AM, Leif Halvard Silli wrote:
>> It is not reading between the line, it is reading while being inspired
>> by CSS21. In CSS21 every 'simple selector' - or as CSS3 puts it, every
>> 'simple selector sequence', is said to be either a type selector or a
>> universal selector:
>
> I'm not following this. Why are we using definitions and concepts from
> one specification to "interpret" another specification, which uses quite
> different definitions and concepts?

Because this sentence in CSS 3 Selectors,

"If the universal selector is not the only component of a
sequence of simple selectors, the * may be omitted"

which is lifted directly out of CSS 2.1, offer us too little
friction against thinking along the lines defined in CSS 2.1.

The test suite of CSS Selectors Level 3 consequently uses the
wording "omitted universal selector".[1][2][3] It doesn't simply
say "omitted *", as the draft does. Do you agree that CSS
Selectors Level 3 should say the same thing?

Here is a text proposal:

"If the universal selector is not the only component of a
sequence of simple selectors and if it also is without the
namespace component, then the universal selector may be omitted."

[1] http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/xhtml/
[2] http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/html/
[3] http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/xml/
--
leif halvard silli

Re: [CSSWG] Release Candidate for CSS Namespaces Test Suite

2009-09-29T09:58:02Z

Anne van Kesteren On 09-09-29 16.18:

> On Tue, 29 Sep 2009 16:03:06 +0200, Leif Halvard Silli :
>> I just argued, in a reply to Øyvind, that it is. It would be nice to
>> know exactly why it is not an error - if it isn't one.
>
> It is not an error per the grammar or the prose of Selectors. Such rules
> need to be rejected.

See the other "subthread".

>>> This has nothing to do with the @namespace construct.
>> If you want *.class{} to select an element inside a SVG file - or
>> section, then it is useful to have a test that shows that
>>
>> svgNamespaceLinkedPrefix|*.class{}
>>
>> works, no?
>
> Ah, I thought you meant something else. I suppose we could add that, yes.

I guess I changed my goal during the discussion ...

>>>> 5. The XMLNS namespace, is it necessary to declare it?
>>> Yes. There's nothing in the CSS namespaces draft that suggests it is
>>> special. CSS namespaces are independent of XML namespaces.
>> Ok. Do you then agree that tests that catches the error which Firefox is
>> currently having, is needed?
>
> Sure, if you contribute one.

Fine.

>>>> 6. The XML namespace, is it necessary to declare it via @namespace?
>>> Yes.
>> Same note as above: do you agree that tests that catches the Firefox
>> error is needed?
>
> Sure.

Fine.

>>>> 9. text/html namespace tests!
>>> Since HTML5 is far away and it is not strictly needed I'd rather
>>> avoid testing this for now and assume it will work down the road given
>>> that the DOM model is identical.
>> Well, I would argue the opposite - and I would not mix HTML 5 into the
>> issue at all (even if I perhaps did ...):
>>
>> * In order to prove that CSS @namespace is completely unrelated to
>> the namespaces of the host language, it would be useful to have tests
>> for text/html. Text/html is here today.
>> * Also, I guess one may already link the same CSS file to both XHTML
>> and HTML - and SVG etc - files. So it is already relevant.
>>
>> It is also very simple: The two tests pages I made are identical (except
>> for one line of info in the start) - they are just served differently.
>> I guess you don't say no thanks, if I offer them ...
>
> Since the requirements of namespaces in the HTML DOM are changing between
> HTML4 and HTML5 and user agents are somewhere in middle collectively it
> seems unwise to test this until the new approach is fully done. The new
> approach happens to be named HTML5.

For tests which only seek to see whether selector sequences are
considered valid by the UA - independently of the host language, I
cannot see that HTML 5 matters.

However, I agree that testing whether a "namespaced selector
sequence" actually matches anything inside a text/html document,
should not start, yet.
--
leif halvard silli

Re: [CSSWG] Release Candidate for CSS Namespaces Test Suite

2009-09-29T09:07:11Z

On Tue, 29 Sep 2009 17:57:22 +0200, Leif Halvard Silli
<xn--mlform-iua@målform.no> wrote:
> Anne van Kesteren On 09-09-29 15.24:
>> The point of these lines is that the namespace_prefix is tied to the
>> *. If you omit the * you cannot use the namespace_prefix.
>
> My view is not interesting. I was just testing UA.
>
> In Webkit the above is simply interpreted to say that we cannot do
> this: ns|{}. Webkit did not interpret it as saying that one cannot do
> this: ns|[attr]{}.

Bug in WebKit.

> [...]
>
> Rather than saying that "the * may be omitted", it should say that the
> 'universal selector' may be dropped. (Or else it could just as well have
> said that the type selector could have been dropped - as the grammar in
> fact show you can - of course it may then select other elements.)
>
> This focus on the character '*' makes it seem as if there is a shorthand
> for the universal selector - namely to drop it.

The specification could be clearer I suppose.

> What do you mean by 'non-namespace cases'? *|*{} is also a non-namespace
> case.

I mean non-vertical bar cases then. The Selectors specification agrees
with how put it, but if you want to view things in a rather different way
I suppose non-vertical bar cases work.

>> No, that is reading between the lines. (And contrary to the grammar.)
>> Your further examples seem all along the same lines of not reading
>> the specification literally and trying to infer things that are not
>> there.
>
> It is not reading between the line, it is reading while being inspired
> by CSS21.

That is called reading between the lines.

--
Anne van Kesteren
http://annevankesteren.nl/