W3C home > Mailing lists > Public > www-dom-ts@w3.org > June 2003

RE: Capitalization issues

From: Mary Brady <mbrady@nist.gov>
Date: Wed, 25 Jun 2003 14:03:51 -0400
To: "'Curt Arnold'" <carnold@houston.rr.com>, "'David Faure'" <faure@kde.org>
Cc: <www-dom-ts@w3.org>, <staikos@kde.org>
Message-ID: <001301c33b44$229b16b0$293b0681@sdct.nist.gov>

I have to say I haven't really been following this discussion much and 
Rick is on vacation, but I did poke around a bit and found the following
message, which gives some ideas on the original intent of these tests.
I'm not sure how they have been modified since the initial release, but 
hopefully this will help...I'll try to look a little closer as well.



-----Original Message-----
From: www-dom-ts-request@w3.org [mailto:www-dom-ts-request@w3.org] On
Behalf Of Curt Arnold
Sent: Wednesday, June 25, 2003 1:07 PM
To: David Faure
Cc: www-dom-ts@w3.org; staikos@kde.org
Subject: Re: Capitalization issues

David Faure wrote:

>Many tests fail in Konqueror (and almost certainly Safari, maybe other 
>browsers too) due to a capitalization issue.
>For instance hc_attrname.html expects "class" but since the document
>is HTML, we return "CLASS", as per the HTML specification.
>According to Curt Arnold this would be (from memory) because the
>spec says uppercase, but since Mozilla and IE return lowercase,
>the tests were changed to expect lowercase.
>But this completely screws up any browser that attempts to actually
>to the DOM spec, which is what this is all about, isn't it?
>If the tests accept that Mozilla and IE return lowercase, why not
>accept both (the "Mozilla and IE" way, and the "compliant" way, i.e.
>PS: congratulations for the improvements to the test suite. It looks
>more complete now, it catches many little unimplemented things - which
>I'm fixing one by one :)
I'm digging into this right now, my recollection is fuzzy and I've not 
been able to find the "spec doesn't say what it appears to say" message 
that I recalled.

David's observation is about test failures with Level 1 Core hc_* tests.

hc_attrname is an example of one of the tests that is failing on 
Konqueror where it checks the nodeName of a "class" attribute.  The 
original version of hc_attrname.xml 
which was checked in by dom_ts_2 (Rick Rivello?) on 8 March 2002 
specified ignoreCase="auto" which would have required an HTML 
implementation to return "CLASS" (as Konqueror is now doing).   On 10 
June 2002 (as part of a massive update to the HTML compatible Core 
tests), I checked in a modified version that specified 
ignoreCase="false" that would require an HTML implementation to return 
"class" (which is the case of the attribute in the source document). 

By my reading of 
ignoreCase="auto" (upper case for HTML implementations, lower case for 
XHTML) would be correct.

I have recollections of ignoreCase being misused 
(http://lists.w3.org/Archives/Public/www-dom-ts/2002Mar/0020.html point 
5) in the initial L1 Core HTML compatible tests.  So the change from 
ignoreCase="auto" to ignoreCase="false" might be a side-effect of a 
global change to reset everything to the most restrictive setting with 
the intention of later restoring those that should have had other

Here is a listing of previous messages that touched on the subject of 
case in HTML DOM's:


I'm continuing to explore this issue.
Received on Wednesday, 25 June 2003 14:05:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:06 UTC