CSS2.1 and CSS3 Print Tests

[Tom Clancy-2]

Attached please find tests for CSS2.1 and CSS3 print compliance.

Thanks,

Tom Clancy

[Arron Eicholz]

Robert Stam wrote:

> Chapter_4\bad-selector.htm: do not include & in css style, because it will be
> an incorrect entity, use CDATA section.
> Chapter_4\invalid-decl-at-rule-001.htm: do not include & in css style, because
> it will be an incorrect entity, use CDATA section.
> Chapter_4\escaped-ident-001.htm: '&' character should be escaped in id.
> Chapter_4\escaped-ident-spaces-001.htm: '&' character should be escaped in id.
> Chapter_12\before-location-001.htm: incorrect '<' character.
> Chapter_14\Properties\Background-repeat\background-repeat-005.htm: </p> missing
> Chapter_16\white-space-009.htm: [nowrap] attribute may not be placed in XHTML.
> Chapter_16\white-space-011.htm: [wrap] attribute may not be placed in XHTML.

Chapter_4\bad-selector.htm: is flagged as invalid and does not need to validate
Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and does not need to validate
Chapter_4\escaped-ident-001.htm: This case now flagged as invalid
Chapter_4\escaped-ident-spaces-001.htm: This case now flagged as invalid
Chapter_12\before-location-001.htm: '<' character is now properly changed to <
Chapter_14\Properties\Background-repeat\background-repeat-005.htm: <p> tag is now closed properly
Chapter_16\white-space-009.htm: attribute corrected to be valid HTML but case is flagged as HTMLonly.
Chapter_16\white-space-011.htm: case correct to be valid. Attribute removed.

These changes will be in our next release of test files. Thank you for submitting these issues.

--
Thanks,
Arron Eicholz

[Anne van Kesteren-2]

On Fri, 04 Apr 2008 00:17:25 +0200, Arron Eicholz  
<Arron.Eicholz@...> wrote:

> Robert Stam wrote:
>> Chapter_4\bad-selector.htm: do not include & in css style, because it  
>> will be
>> an incorrect entity, use CDATA section.
>> Chapter_4\invalid-decl-at-rule-001.htm: do not include & in css style,  
>> because
>> it will be an incorrect entity, use CDATA section.
>> Chapter_4\escaped-ident-001.htm: '&' character should be escaped in id.
>> Chapter_4\escaped-ident-spaces-001.htm: '&' character should be escaped  
>> in id.
>> Chapter_12\before-location-001.htm: incorrect '<' character.
>> Chapter_14\Properties\Background-repeat\background-repeat-005.htm: </p>  
>> missing
>> Chapter_16\white-space-009.htm: [nowrap] attribute may not be placed in  
>> XHTML.
>> Chapter_16\white-space-011.htm: [wrap] attribute may not be placed in  
>> XHTML.
>
> Chapter_4\bad-selector.htm: is flagged as invalid and does not need to  
> validate
> Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and does  
> not need to validate
> Chapter_4\escaped-ident-001.htm: This case now flagged as invalid
> Chapter_4\escaped-ident-spaces-001.htm: This case now flagged as invalid
> Chapter_12\before-location-001.htm: '<' character is now properly  
> changed to <
> Chapter_14\Properties\Background-repeat\background-repeat-005.htm: <p>  
> tag is now closed properly
> Chapter_16\white-space-009.htm: attribute corrected to be valid HTML but  
> case is flagged as HTMLonly.
> Chapter_16\white-space-011.htm: case correct to be valid. Attribute  
> removed.

Note that flagging them as invalid doesn't help if they're actual XML  
files as they would simply not parse. That would also mean they can't be  
used in the CSS test case framework which requires well-formed tests.


> These changes will be in our next release of test files. Thank you for  
> submitting these issues.

Any chance you guys can give us an ETA? Since you already released these  
tests, just updating the public ones per your comments here shouldn't be  
too much trouble, right? ;-)


--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

[fantasai]

Arron Eicholz wrote:

> Robert Stam wrote:
>> Chapter_4\bad-selector.htm: do not include & in css style, because it will be
>> an incorrect entity, use CDATA section.
>> Chapter_4\invalid-decl-at-rule-001.htm: do not include & in css style, because
>> it will be an incorrect entity, use CDATA section.
>> Chapter_4\escaped-ident-001.htm: '&' character should be escaped in id.
>> Chapter_4\escaped-ident-spaces-001.htm: '&' character should be escaped in id.
>> Chapter_12\before-location-001.htm: incorrect '<' character.
>> Chapter_14\Properties\Background-repeat\background-repeat-005.htm: </p> missing
>> Chapter_16\white-space-009.htm: [nowrap] attribute may not be placed in XHTML.
>> Chapter_16\white-space-011.htm: [wrap] attribute may not be placed in XHTML.
>
> Chapter_4\bad-selector.htm: is flagged as invalid and does not need to validate
> Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and does not need to validate
> Chapter_4\escaped-ident-001.htm: This case now flagged as invalid
> Chapter_4\escaped-ident-spaces-001.htm: This case now flagged as invalid
> Chapter_12\before-location-001.htm: '<' character is now properly changed to <
> Chapter_14\Properties\Background-repeat\background-repeat-005.htm: <p> tag is now closed properly
> Chapter_16\white-space-009.htm: attribute corrected to be valid HTML but case is flagged as HTMLonly.
> Chapter_16\white-space-011.htm: case correct to be valid. Attribute removed.
>
> These changes will be in our next release of test files. Thank you for submitting these issues.

Hi Arron,
As Anne points out, all of these tests need to validate as XHTML.
If they are testing invalid CSS, then they shouldn't pass the
*CSS* validator, but they do need to validate as XHTML. Robert's
suggetion of using a CDATA section would be the easiest way to
fix the tests where CSS data is tripping up the XML parser.

Thanks~

~fantasai

[Arron Eicholz]

fantasai wrote:

> As Anne points out, all of these tests need to validate as XHTML.
> If they are testing invalid CSS, then they shouldn't pass the
> *CSS* validator, but they do need to validate as XHTML. Robert's
> suggetion of using a CDATA section would be the easiest way to
> fix the tests where CSS data is tripping up the XML parser.

I agree that cases should validate but there are some exceptions. When the case is flagged HTMLonly it doesn't necessarily have to validate as XHTML does it? Those cases might not validate for XHTML. There could be all sorts of deprecated attributes and tags in there that might not allow XHTML to validate but would be perfectly fine in HTML.

Chapter_4\bad-selector.htm: Corrected with a CDATA
Chapter_4\invalid-decl-at-rule-001.htm: corrected with CDATA
Chapter_4\escaped-ident-001.htm: Corrected to use dash and underscore
Chapter_4\escaped-ident-spaces-001.htm: corrected to use dash and underscore
Chapter_16\white-space-009.htm: attribute corrected to be valid HTML but case is flagged as HTMLonly.

Side question... If an 'id' is invalid (i.e. "B&W?") should you still be able to match the invalid 'id' using CSS? 'id' attributes can't contain '&' or '?' so I am thinking there should be no way to match in this case since the 'id' is invalid but I'm want to confirm this.

--
Thanks,
Arron Eicholz

> -----Original Message-----
> From: fantasai [mailto:fantasai.lists@...]
> Sent: Thursday, April 03, 2008 5:11 PM
> To: Arron Eicholz
> Cc: Robert Stam; public-css-testsuite@...
> Subject: Re: Not compliant XHTML MS tests.
>
> Arron Eicholz wrote:
> > Robert Stam wrote:
> >> Chapter_4\bad-selector.htm: do not include & in css style, because
> it will be
> >> an incorrect entity, use CDATA section.
> >> Chapter_4\invalid-decl-at-rule-001.htm: do not include & in css
> style, because
> >> it will be an incorrect entity, use CDATA section.
> >> Chapter_4\escaped-ident-001.htm: '&' character should be escaped in
> id.
> >> Chapter_4\escaped-ident-spaces-001.htm: '&' character should be
> escaped in id.
> >> Chapter_12\before-location-001.htm: incorrect '<' character.
> >> Chapter_14\Properties\Background-repeat\background-repeat-005.htm:
> </p> missing
> >> Chapter_16\white-space-009.htm: [nowrap] attribute may not be placed
> in XHTML.
> >> Chapter_16\white-space-011.htm: [wrap] attribute may not be placed
> in XHTML.
> >
> > Chapter_4\bad-selector.htm: is flagged as invalid and does not need
> to validate
> > Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and
> does not need to validate
> > Chapter_4\escaped-ident-001.htm: This case now flagged as invalid
> > Chapter_4\escaped-ident-spaces-001.htm: This case now flagged as
> invalid
> > Chapter_12\before-location-001.htm: '<' character is now properly
> changed to <
> > Chapter_14\Properties\Background-repeat\background-repeat-005.htm:
> <p> tag is now closed properly
> > Chapter_16\white-space-009.htm: attribute corrected to be valid HTML
> but case is flagged as HTMLonly.
> > Chapter_16\white-space-011.htm: case correct to be valid. Attribute
> removed.
> >
> > These changes will be in our next release of test files. Thank you
> for submitting these issues.
>
> Hi Arron,
> As Anne points out, all of these tests need to validate as XHTML.
> If they are testing invalid CSS, then they shouldn't pass the
> *CSS* validator, but they do need to validate as XHTML. Robert's
> suggetion of using a CDATA section would be the easiest way to
> fix the tests where CSS data is tripping up the XML parser.
>
> Thanks~
>
> ~fantasai

[Anne van Kesteren-2]

On Fri, 04 Apr 2008 17:55:59 +0200, Arron Eicholz  
<Arron.Eicholz@...> wrote:
> I agree that cases should validate but there are some exceptions. When  
> the case is flagged HTMLonly it doesn't necessarily have to validate as  
> XHTML does it? Those cases might not validate for XHTML. There could be  
> all sorts of deprecated attributes and tags in there that might not  
> allow XHTML to validate but would be perfectly fine in HTML.

HTML and XHTML share the same vocabulary, so I don't think that's true.

> Chapter_4\bad-selector.htm: Corrected with a CDATA
> Chapter_4\invalid-decl-at-rule-001.htm: corrected with CDATA
> Chapter_4\escaped-ident-001.htm: Corrected to use dash and underscore
> Chapter_4\escaped-ident-spaces-001.htm: corrected to use dash and  
> underscore
> Chapter_16\white-space-009.htm: attribute corrected to be valid HTML but  
> case is flagged as HTMLonly.
>
> Side question... If an 'id' is invalid (i.e. "B&W?") should you still be  
> able to match the invalid 'id' using CSS? 'id' attributes can't contain  
> '&' or '?' so I am thinking there should be no way to match in this case  
> since the 'id' is invalid but I'm want to confirm this.

Yes, you should still be able to do that. Though you may need to use  
character escapes because you can not use all characters directly in CSS.  
(Just like you can still do document.getElementById("B&W?") for such  
elements.)


--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

[Arron Eicholz]

Anne van Kesteren wrote:

> > I agree that cases should validate but there are some exceptions.
> When
> > the case is flagged HTMLonly it doesn't necessarily have to validate
> as
> > XHTML does it? Those cases might not validate for XHTML. There could
> be
> > all sorts of deprecated attributes and tags in there that might not
> > allow XHTML to validate but would be perfectly fine in HTML.
>
> HTML and XHTML share the same vocabulary, so I don't think that's true.

XHTML does not support the 'nowrap' attribute on the 'td' tag. This case is specifically called out in the whitespace section of the CSS spec and this is one case that will not validate as XHTML. I'm sure there are others but this is one that I know isn't valid in XHTML.

--
Thanks,
Arron Eicholz

[Anne van Kesteren-2]

On Fri, 04 Apr 2008 18:36:43 +0200, Arron Eicholz  
<Arron.Eicholz@...> wrote:
> XHTML does not support the 'nowrap' attribute on the 'td' tag. This case  
> is specifically called out in the whitespace section of the CSS spec and  
> this is one case that will not validate as XHTML. I'm sure there are  
> others but this is one that I know isn't valid in XHTML.

It validates as XHTML 1.0 Transitional, just like it validates in HTML  
4.01 Transitional... (Though XHTML 1.1 is slightly different, yes, and I  
guess that's what the test suite format is in.)


--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

[fantasai]

Arron Eicholz wrote:

> Anne van Kesteren wrote:
>
>>> I agree that cases should validate but there are some exceptions.
>> When
>>> the case is flagged HTMLonly it doesn't necessarily have to validate
>> as
>>> XHTML does it? Those cases might not validate for XHTML. There could
>> be
>>> all sorts of deprecated attributes and tags in there that might not
>>> allow XHTML to validate but would be perfectly fine in HTML.
>> HTML and XHTML share the same vocabulary, so I don't think that's true.
>
> XHTML does not support the 'nowrap' attribute on the 'td' tag. This
> case is specifically called out in the whitespace section of the
> CSS spec and this is one case that will not validate as XHTML. I'm
> sure there are others but this is one that I know isn't valid in XHTML.

Then make it at least be well-formed XML.

~fantasai

[fantasai]

Arron Eicholz wrote:

> Anne van Kesteren wrote:
>
>>> I agree that cases should validate but there are some exceptions.
>> When
>>> the case is flagged HTMLonly it doesn't necessarily have to validate
>> as
>>> XHTML does it? Those cases might not validate for XHTML. There could
>> be
>>> all sorts of deprecated attributes and tags in there that might not
>>> allow XHTML to validate but would be perfectly fine in HTML.
>> HTML and XHTML share the same vocabulary, so I don't think that's true.
>
> XHTML does not support the 'nowrap' attribute on the 'td' tag. This
> case is specifically called out in the whitespace section of the
> CSS spec and this is one case that will not validate as XHTML. I'm
> sure there are others but this is one that I know isn't valid in XHTML.

Then for these cases make sure it is at least well-formed XML.

~fantasai

[Alan Gresley-2]

Arron Eicholz wrote:
> fantasai wrote:
>
>> As Anne points out, all of these tests need to validate as XHTML.
>> If they are testing invalid CSS, then they shouldn't pass the
>> *CSS* validator, but they do need to validate as XHTML. Robert's
>> suggetion of using a CDATA section would be the easiest way to
>> fix the tests where CSS data is tripping up the XML parser.
>
> I agree that cases should validate but there are some exceptions.
 > when the case is flagged HTMLonly it doesn't necessarily have
 > to validate as XHTML does it? Those cases might not validate
 > for XHTML. There could be all sorts of deprecated attributes
 > and tags in there that might not allow XHTML to validate
 > but would be perfectly fine in HTML.
>
 > Thanks,
 > Arron Eicholz


If the markup is like as you described you should be using a XHTML
traditional Doctype. Then the markup would pass validation.

Alan

[Arron Eicholz]

fantasai wrote:
>> Arron Eicholz wrote:
>>
>> XHTML does not support the 'nowrap' attribute on the 'td' tag. This
>> case is specifically called out in the whitespace section of the
>> CSS spec and this is one case that will not validate as XHTML. I'm
>> sure there are others but this is one that I know isn't valid in XHTML.
>
> Then for these cases make sure it is at least well-formed XML.

I have made the case valid XML. It will not validate for XHTML 1.1 per the test suite standard. The case is marked as HTMLonly and should, when the suite is built, only build out an HTML version.

--
Thanks,
Arron Eicholz

[fantasai]

Tom Clancy wrote:
> Attached please find tests for CSS2.1 and CSS3 print compliance.

at-page-002-f.xht checked in as
   http://dev.w3.org/CSS/css3-page-test-suite/src/page-borders-000.xht
with the title changed to
   @page border shorthand (absolute units)
and the instructions changed to
   This paragraph must appear inside a box with a 1in thick green border.
(made 1" into 1in).

at-page-003.xht checked in as
   http://dev.w3.org/CSS/css3-page-test-suite/src/page-properties-001.xht
with the title changed to
   @page width and height
and a rel="help" link added to
   http://www.w3.org/TR/css3-page/#page-properties

at-page-rule-004.xht is incorrect
You need to specify margins as well as size before you know what size
the border box will be.

page-properties-001.xht checked in as
   http://dev.w3.org/CSS/css3-page-test-suite/src/page-background-000.xht

~fantasai

[Grant, Melinda]

Why is '1in' better than '1"'?  Assuming the tester doesn't know CSS syntax, I would prefer '1 inch', my second preference would be '1"', and I would worry that the tester might not understand '1in'.

Best wishes,

Melinda

> -----Original Message-----
> From: public-css-testsuite-request@...
> [mailto:public-css-testsuite-request@...] On Behalf Of fantasai
> Sent: Monday, April 28, 2008 3:57 PM
> To: Tom Clancy
> Cc: public-css-testsuite@...
> Subject: Re: CSS2.1 and CSS3 Print Tests
>
>
> Tom Clancy wrote:
> > Attached please find tests for CSS2.1 and CSS3 print compliance.
>
> at-page-002-f.xht checked in as
>    http://dev.w3.org/CSS/css3-page-test-suite/src/page-borders-000.xht
> with the title changed to
>    @page border shorthand (absolute units) and the
> instructions changed to
>    This paragraph must appear inside a box with a 1in thick
> green border.
> (made 1" into 1in).
>
> at-page-003.xht checked in as
>
> http://dev.w3.org/CSS/css3-page-test-suite/src/page-properties-001.xht
> with the title changed to
>    @page width and height
> and a rel="help" link added to
>    http://www.w3.org/TR/css3-page/#page-properties
>
> at-page-rule-004.xht is incorrect
> You need to specify margins as well as size before you know
> what size the border box will be.
>
> page-properties-001.xht checked in as
>
> http://dev.w3.org/CSS/css3-page-test-suite/src/page-background-000.xht
>
> ~fantasai
>
>

[fantasai]

Grant, Melinda wrote:
>
> Why is '1in' better than '1"'?  Assuming the tester doesn't know CSS syntax, I would prefer '1
> inch', my second preference would be '1"', and I would worry that the tester might not understand
> '1in'.

"1 inch" would be better, but 'in' is a standard abbreviation of an inch
and it's more explicit than 1". I'd rather not be too American-centric
here: there are layout engine developers in Europe and Japan, too, and
I'd imagine they'd have an easier time looking up {in means inch} than
{" means inch}.

~fantasai

[David Arakelian]

I'm new here and just thought I'd post my two cents. The other CSS
measurements use their alphabetic abbreviations, e.g. cm, ex etc. with
the exception of %. % may have been abbreviated as pc if it weren't for
the use of pc for pica. I think it would be best to stay with in rather
than get things mixed up. I would rather type out 1 cm than 1
centimetre. Remember that this is spelt different here in the UK too.


--
      ,'/:.          David Arakelian
    ,'-/::::.        http://www.theatons.com/
  ,'--/::(@)::.      Web Security Consultant
,'---/::::::::::.    Wales
____/:::::::::::::.  
  T H E A T O N S  

[fantasai]

Robert Stam wrote:
> Hi,
>
> I believe in CSS level 2.1 test t060402-c31-important-00-b should
> display 2 green lines and than the third line red.
> Because the specificity for the style= is 1,0,0,0 so will be more
> important (even above the important from the styles from the style
> block)  
>
> How do you think about this?

Actually, the p { color: green !important; } rule wins. It is less
specific, but it has more weight. See
   http://www.w3.org/TR/CSS21/cascade.html#cascading-order

~fantasai

[Robert Stam]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

 

Some (26) test documents from the Microsoft suite  (available at: http://samples.msdn.microsoft.com/csstestpages/default.htm) are not compliant XHTML (not well-formed or wrongly escaped).

I know some (or maybe all) of them are flagged as HTMLOnly, but I think it should be preferred if

the XML is well-formed all the times.

 

Chapter_4\Rules\counters-002.htm: The '"' character, hexadecimal value 0x22, cannot be included in a name. Line 23, position 13.

Proposed solution: Remove " character.

 

Chapter_4\Rules\ident-001.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\ident-003.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\ident-004.htm: Name cannot begin with the '1' character, hexadecimal value 0x31. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the 1 in the attribute name)

 

Chapter_4\Rules\ident-005.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\invalid-decl-at-rule-001.htm: An error occurred while parsing EntityName. Line 16, position 21.

Proposed solution: Add CDATA section in <style type="text/css">

 

Please see the BETA1 submit also:

---------

Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and does not need to validate

 

Hi Arron,

As Anne points out, all of these tests need to validate as XHTML.

If they are testing invalid CSS, then they shouldn't pass the

*CSS* validator, but they do need to validate as XHTML. Robert's suggetion of using a CDATA section would be the easiest way to fix the tests where CSS data is tripping up the XML parser.

 

Thanks~

 

~fantasai

--------

 

 

Chapter_4\Rules\uri-004.htm: An error occurred while parsing EntityName. Line 13, position 61.

Proposed solution: Add CDATA section in <style type="text/css">

 

Chapter_5\Rules\attribute-value-selector-004.htm: Name cannot begin with the '1' character, hexadecimal value 0x31. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the 1 in the attribute name).

 

Chapter_6\Rules\HTML-attribute-023.htm: '/'is an unexpected token. The expected token is '='. Line 18, position 21.

Proposed solution: replace with <hr noshade="true" />

 

Chapter_6\Rules\HTML-attribute-024.htm: '>'is an unexpected token. The expected token is '='. Line 28 and 29, position 27.

Proposed solution: replace with <td nowrap="true"

 

Chapter_6\Rules\user-stylesheet-002.htm: The 'p' start tag on line 14 does not match the end tag of 'body'. Line 16, position 7.

Proposed solution: replace last <p> on line 'Test passes if there is a green box below.' with </p>

 

Chapter_7\Rules\media-dependency-012.htm: The 'body' start tag on line 19 does not match the end tag of 'html'. Line 24, position 3.

Proposed solution: remove duplicated <body>

 

Chapter_9\Rules\viewport-004.htm: The 'frame' start tag on line 14 does not match the end tag of 'frameset'. Line 20, position 7.

Proposed solution: close frame like <frame src="../../Support/viewport-004-firstcanvas.htm" />

Notice that <frameset is not supported in XHTML 1.1

 

Chapter_16\Rules\text-001.htm: '▬', hexadecimal value 0x16, is an invalid character. Line 25, position 29.

Proposed solution: Add <?xml version="1.0" encoding="UTF-8"?> as header in the file

 

Chapter_16\Rules\white-space-009.htm: '>' is an unexpected token. The expected token is '='. Line 33, position 27.

Proposed solution: replace with <td nowrap="true">

 

Chapter_16\Rules\white-space-011.htm: '>' is an unexpected token. The expected token is '='. Line 24, position 18.

Proposed solution: replace with <pre wrap="true">

 

Chapter_17\Rules\border-conflict-example-001.htm: The 'TD' start tag on line 42 does not match the end tag of 'TR'. Line 43, position 15.

Proposed solution: Close all TD elements (as well the COL).

Notice that XHTML requires lowercase element names [we can notice that the HTMLonly flag].

 

Chapter_17\Rules\border-conflict-example-002.htm: '"' is an unexpected token. The expected token is '='. Line 9, position 20.

Proposed solution: Add an '=' so we have <style type="text/css">

 

Chapter_17\Rules\table-caption-optional-002.htm: The 'div' start tag on line 33 does not match the end tag of 'span'. Line 56, position 15.

Proposed solution: Remove the endtag on line 56  </span>

 

Chapter_17\Rules\table-height-algorithm-016.htm: '<' is an unexpected token. The expected token is '>'. Line 35, position 70.

Proposed solution: Add additional > to line 35 so we have <div id="small">FillerText</div>

 

Chapter_17\Rules\table-height-algorithm-030.htm: The 'body' start tag on line 28 does not match the end tag of 'p'. Line 30, position 11.

Proposed solution: Remove </p> on line 30

 

Chapter_17\Rules\table-intro-example-001.htm: The 'td' start tag on line 39 does not match the end tag of 'table'. Line 40,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-002.htm: The 'td' start tag on line 39 does not match the end tag of 'table'. Line 40,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-003.htm: The 'td' start tag on line 37 does not match the end tag of 'table'. Line 38,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-004.htm: The 'td' start tag on line 34 does not match the end tag of 'table'. Line 35,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-layer-transparency-example-001.htm: The 'td' start tag on line 36 does not match the end tag of 'table'. Line 37, position 11.

Proposed solution: close all tags (tr and td) properly

 

Please let me know if you want to receive the updated files as well.

 

Best Regards,

Robert Stam

 

TallComponents

 

[Robert Stam]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

 

At Chapter_16\Rules\text-001.htm: '▬', hexadecimal value 0x16, is an invalid character. Line 25, position 29.

The proposed solution is incorrect and should be:

Proposed solution: change line 25 into <div id="testDiv">X &#022; X</div>

 

Best Regards,

Robert Stam

 

TallComponents

 

From: public-css-testsuite-request@... [mailto:public-css-testsuite-request@...] On Behalf Of Robert Stam
Sent: Tuesday, September 02, 2008 9:20 PM
To: public-css-testsuite@...
Cc: Arron.Eicholz@...; Chris.Wilson@...; fantasai.lists@...
Subject: Not compliant XHTML MS tests (IE8, BETA2)

 

Hi,

 

Some (26) test documents from the Microsoft suite  (available at: http://samples.msdn.microsoft.com/csstestpages/default.htm) are not compliant XHTML (not well-formed or wrongly escaped).

I know some (or maybe all) of them are flagged as HTMLOnly, but I think it should be preferred if

the XML is well-formed all the times.

 

Chapter_4\Rules\counters-002.htm: The '"' character, hexadecimal value 0x22, cannot be included in a name. Line 23, position 13.

Proposed solution: Remove " character.

 

Chapter_4\Rules\ident-001.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\ident-003.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\ident-004.htm: Name cannot begin with the '1' character, hexadecimal value 0x31. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the 1 in the attribute name)

 

Chapter_4\Rules\ident-005.htm: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the - in the attribute name)

 

Chapter_4\Rules\invalid-decl-at-rule-001.htm: An error occurred while parsing EntityName. Line 16, position 21.

Proposed solution: Add CDATA section in <style type="text/css">

 

Please see the BETA1 submit also:

---------

Chapter_4\invalid-decl-at-rule-001.htm: is flagged as invalid and does not need to validate

 

Hi Arron,

As Anne points out, all of these tests need to validate as XHTML.

If they are testing invalid CSS, then they shouldn't pass the

*CSS* validator, but they do need to validate as XHTML. Robert's suggetion of using a CDATA section would be the easiest way to fix the tests where CSS data is tripping up the XML parser.

 

Thanks~

 

~fantasai

--------

 

 

Chapter_4\Rules\uri-004.htm: An error occurred while parsing EntityName. Line 13, position 61.

Proposed solution: Add CDATA section in <style type="text/css">

 

Chapter_5\Rules\attribute-value-selector-004.htm: Name cannot begin with the '1' character, hexadecimal value 0x31. Line 18, position 12.

Proposed solution: Remove invalid test (or maybe escape the 1 in the attribute name).

 

Chapter_6\Rules\HTML-attribute-023.htm: '/'is an unexpected token. The expected token is '='. Line 18, position 21.

Proposed solution: replace with <hr noshade="true" />

 

Chapter_6\Rules\HTML-attribute-024.htm: '>'is an unexpected token. The expected token is '='. Line 28 and 29, position 27.

Proposed solution: replace with <td nowrap="true"

 

Chapter_6\Rules\user-stylesheet-002.htm: The 'p' start tag on line 14 does not match the end tag of 'body'. Line 16, position 7.

Proposed solution: replace last <p> on line 'Test passes if there is a green box below.' with </p>

 

Chapter_7\Rules\media-dependency-012.htm: The 'body' start tag on line 19 does not match the end tag of 'html'. Line 24, position 3.

Proposed solution: remove duplicated <body>

 

Chapter_9\Rules\viewport-004.htm: The 'frame' start tag on line 14 does not match the end tag of 'frameset'. Line 20, position 7.

Proposed solution: close frame like <frame src="../../Support/viewport-004-firstcanvas.htm" />

Notice that <frameset is not supported in XHTML 1.1

 

Chapter_16\Rules\text-001.htm: '▬', hexadecimal value 0x16, is an invalid character. Line 25, position 29.

Proposed solution: Add <?xml version="1.0" encoding="UTF-8"?> as header in the file

 

Chapter_16\Rules\white-space-009.htm: '>' is an unexpected token. The expected token is '='. Line 33, position 27.

Proposed solution: replace with <td nowrap="true">

 

Chapter_16\Rules\white-space-011.htm: '>' is an unexpected token. The expected token is '='. Line 24, position 18.

Proposed solution: replace with <pre wrap="true">

 

Chapter_17\Rules\border-conflict-example-001.htm: The 'TD' start tag on line 42 does not match the end tag of 'TR'. Line 43, position 15.

Proposed solution: Close all TD elements (as well the COL).

Notice that XHTML requires lowercase element names [we can notice that the HTMLonly flag].

 

Chapter_17\Rules\border-conflict-example-002.htm: '"' is an unexpected token. The expected token is '='. Line 9, position 20.

Proposed solution: Add an '=' so we have <style type="text/css">

 

Chapter_17\Rules\table-caption-optional-002.htm: The 'div' start tag on line 33 does not match the end tag of 'span'. Line 56, position 15.

Proposed solution: Remove the endtag on line 56  </span>

 

Chapter_17\Rules\table-height-algorithm-016.htm: '<' is an unexpected token. The expected token is '>'. Line 35, position 70.

Proposed solution: Add additional > to line 35 so we have <div id="small">FillerText</div>

 

Chapter_17\Rules\table-height-algorithm-030.htm: The 'body' start tag on line 28 does not match the end tag of 'p'. Line 30, position 11.

Proposed solution: Remove </p> on line 30

 

Chapter_17\Rules\table-intro-example-001.htm: The 'td' start tag on line 39 does not match the end tag of 'table'. Line 40,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-002.htm: The 'td' start tag on line 39 does not match the end tag of 'table'. Line 40,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-003.htm: The 'td' start tag on line 37 does not match the end tag of 'table'. Line 38,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-intro-example-004.htm: The 'td' start tag on line 34 does not match the end tag of 'table'. Line 35,position 11.

Proposed solution: close all tags (tr, th and td) properly

 

Chapter_17\Rules\table-layer-transparency-example-001.htm: The 'td' start tag on line 36 does not match the end tag of 'table'. Line 37, position 11.

Proposed solution: close all tags (tr and td) properly

 

Please let me know if you want to receive the updated files as well.

 

Best Regards,

Robert Stam

 

TallComponents

 

[Robert Stam]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

 

In the following 2 documents I found a little mistake:

 

H4\Rules\number-units-014.htm -- line 8: content="The ’em’ unit is equal to the computed value of the ’font-size’ …

Do not use the Unicode ‘, but use: content="The 'em' unit is equal to the computed value of the 'font-size'

 

H5\Rules\first-letter-selector-007.htm –- line 9: <style>

Include the required type attribute: <style type="text/css">

 

Best Regards,

Robert Stam

 

TallComponents