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

RE: Validating microsoft tests

From: Robert Stam <robert@tallcomponents.com>
Date: Wed, 27 Jan 2010 09:16:57 -0600
Message-ID: <31DBA4F3A35EEE408177B6D1E50A4C5002307D70@34093-C9-EVS1.exchange.rackspace.com>
To: "fantasai" <fantasai.lists@inkedblade.net>, <public-css-testsuite@w3.org>
Hi ~fantasai,

What about the css\chapter_4\Rules\ident-001.htm to 005.htm files
available in the public MS tests?
As well as: css\chapter_5\Rules\attribute-value-selector-004.htm

These tests have attributes that starts with a hyphen or a digit.
I assume that that's not well formed as well. 


Best Regards,
Robert Stam
 
TallComponents
Follow us @ twitter: http://twitter.com/tallcomponents

> -----Original Message-----
> From: public-css-testsuite-request@w3.org
[mailto:public-css-testsuite-
> request@w3.org] On Behalf Of fantasai
> Sent: Wednesday, January 27, 2010 4:06 PM
> To: public-css-testsuite@w3.org
> Subject: Validating microsoft tests
> 
> The following tests are not well-formed:
> 
> at-charset-061.xht
>    This triggers an encoding error in the validator. You probably
should
>    put those Shift-JIS bytes in as numbered character entities. As
long
>    as you don't put the <style> contents in a CDATA section, they
should
>    parse into memory as the bytes you want (when parsed as XML).
> 
> control-characters-001.xht
> white-space-control-characters-001.xht
>    The validator complains about these having invalid xmlChars, and it
>    doesn't parse as XML. You'll need to find some other way of putting
>    these control characters into the document. Maybe using the DOM.
> 
> table-intro-example-*
>    These are missing lots of internal table element end tags.
> 
> overflow-applies-to-004.xht
>    This one has two <body> tags.
> 
> html-attribute-023.xht
>    This one uses a boolean attribute in shorthand, but in XML they
must
>    be written out in full.
>    Also, looking at the test, I don't think it's testing what the
assert
>    says it's testing. To test noshade, you need to compare not the
color,
>    but the style. The noshade attribute indicates a solid (as opposed
to
>    carved-looking) rule, not a color or the ability to take color.
> 
> ~fantasai
Received on Wednesday, 27 January 2010 15:17:36 GMT

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