W3C home > Mailing lists > Public > www-dom-ts@w3.org > March 2002

Re: Using existing staff.xml based tests with HTML processors

From: Mary Brady <mbrady@nist.gov>
Date: Fri, 8 Mar 2002 10:22:52 -0500
Message-ID: <000c01c1c6b5$21456220$9700a8c0@sdct.nist.gov>
To: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Using Curt's files, I just modified attname.xml, with a new
name of hc_attrname.xml -- I'll submit it shortly.  There
were very few changes -- essentially, change "address"
to "abbr" and "street" to "class".  I also had to add
ignorecase="auto".  I'll submit the file -- I haven't
run it yet -- I'm working on a different platform, and
am currently installing the components necessary to
build the test suite.  If someone else runs it, let me know
how it turns out.


----- Original Message -----
From: "Curt Arnold" <carnold@houston.rr.com>
To: <www-dom-ts@w3.org>
Sent: Friday, March 08, 2002 10:13 AM
Subject: Re: Using existing staff.xml based tests with HTML processors

> > I believe it would be more useful to use constructs like <div
> class="employeeid"> and <a class="domestic" href=2xx">
> >
> That would require more substantial changes to the body of the test, since
> the set up in most of the tests use a getElementsByTagName() to locate the
> element that is the focus on the test.  If there is not a one-to-one
> correspondance of an existing tag name to an HTML tag name, then a
> mechanism would have to be used to locate the focal element and the
> tests and the HTML compatible tests would diverge more than necessary.  In
> addition, all tests that retrieved tag names would have to be changed to
> retrieve that class attribute.
> Also, I'm not sure why the differentiating on "class" would be more
> "useful".
> p.s. The file that I suggested last night does display identically in
> Mozilla and IE.  It can be accessed from cvsWeb at
> les/hc_staff.html?
Received on Friday, 8 March 2002 10:24:03 UTC

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