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

Selectors Tests

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Tue, 28 Oct 2008 14:40:17 +0100
Message-ID: <49071641.4000609@lachy.id.au>
To: public-css-testsuite <public-css-testsuite@w3.org>

Hi,
   While preparing the Selectors implementation report for Opera, I came 
across a few issues with the testsuite.

Firstly, I have a few tests for cases that are not tested in the 
testsuite for attribute selectors and the UI state pseudo classes, 
:enabled and :disabled with hidden input controls.

http://lachy.id.au/dev/css/tests/selectors/attribute/
http://lachy.id.au/dev/css/tests/selectors/pseudo-classes/ui/

The attribute selector tests are written based on the previous WG 
resolution that they match nothing.

http://lists.w3.org/Archives/Public/www-style/2008Apr/0038.html

Secondly, the testsuite contains tests for the :indeterminate 
pseudo-class.  However, these tests depend on a proprietary IE extension 
for setting the state of checkboxes to an indeterminate state.  Since we 
don't implement the HTMLInputElement.indeterminate property, nor any 
other controls that can be in an indeterminate state, is it reasonable 
to mark those tests as N/A in the implementation report?

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Tuesday, 28 October 2008 13:41:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 17:51:57 GMT