W3C home > Mailing lists > Public > public-css-testsuite@w3.org > March 2009

Re: attribute-value-selector-004.xht not well formed

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 11 Mar 2009 20:34:29 +0100
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <3j3gr4dsnqncab6qfh52h8lf4c1cjdjo58@hive.bjoern.hoehrmann.de>
* Sylvain Galineau wrote:
>But it does not follow that no test can ever use invalid markup. No test
>suite that aims to be complete can limit itself to valid input. Or
>eliminate a test because the effect it checks for has its cause tested
>somewhere else.

The logic behind the test is this: the selector [1BadAttr] is incorrect
because the digit "1" is not allowed to occur in that position. An im-
plementation that fails to detect this error will most likely success-
fully match the selector against an element with an 1BadAttr attribute.
Given a document with such an element, such an implementation will fail
the test, while others won't. So this is a perfectly sound test.

The problem with the test is that XML and XML-based languages are not
good languages to make elements with 1BadAttr attributes, they do not
allow such attributes, you cannot construct them through the DOM, and
processors do not usually recover from errors so that you end up with
them. Even if only meant to be converted to, say, "HTML5", you'd run
into this problem.

If the document format is changed, the test would be fine.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 11 March 2009 19:35:17 GMT

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