W3C home > Mailing lists > Public > public-css-testsuite@w3.org > May 2012

2 issues with content-attr-002 [nightly-unstable]

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Tue, 1 May 2012 18:13:19 -0400
Message-ID: <4264561dcf4193987c295cbd4d970e68.squirrel@ed-sh-cp3.entirelydigital.com>
To: "Public CSS test suite mailing list" <public-css-testsuite@w3.org>


1- Usually, <link>s are not displayed but, when they do, the default
user agent stylesheet could be making them use the default color for
unvisited <a>. Firefox 12.0 colorize the <link>s in the test with blue;
other browsers (Chrome 18, Opera 11.62, Konqueror 4.8.2) use black
color. Another issue is that, once the reftest is loaded, normally the
4th link in the test should become a visited link, therefore using the
assigned color for :visited links (usually purple-ish color).

2- If the testing browser uses an additional <link> for linking to an
add-on or extension - and this is my case when I use Chrome - , then
this extra <link> situation can not be predicted by the reftest.

Both difficulties make it impossible to do a reliable, trustworthy reftest.

Suggested modification to the code

line 14  link[rel="stylesheet"]:before { color: blue; content: 'The test
has '; }
line 15  link[rel="stylesheet"]:after { color: blue; content:
attr(media); }




Contributions to the CSS 2.1 test suite:

CSS 2.1 Test suite RC6, March 23rd 2011:

CSS 2.1 test suite harness:

Contributing to to CSS 2.1 test suite:
Received on Tuesday, 1 May 2012 22:13:52 UTC

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