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

Re: Concerns regarding the W3 Document Object Model (DOM) Conformance Test Suites

From: Robert Clary <bclary@netscape.com>
Date: Wed, 27 Feb 2002 07:36:11 -0500
Message-ID: <3C7CD2BB.3030307@netscape.com>
To: Manos Batsis <m.batsis@bsnet.gr>
CC: www-dom-ts@w3.org

Thanks for the comment. I suppose my mind set is on Level 2 rather than 
Level 1.

I stand corrected on the issue of DOM Level 1 creating Documents and 
DOMImplementation. However, creating empty Documents via implementation 
specific methods and using the remaining DOM methods to populate the 
test document should still be possible and the preferred approach. I 
still believe the introduction of parser related issues where not 
absolutely required is inappropriate.

For Level 2 tests however the ability to bootstrap the tests from the 
DOMImplementation interface means that external documents are not required.

Memory Management


The DOM Level 2 API does not define a standard way to create 
objects; DOM implementations must provide some proprietary way of 
bootstrapping these DOM interfaces, and then all other objects can be 
built from there.


Interface DOMImplementation


Manos Batsis wrote:

>It makes me very happy to see activity coming from people behind my
>favorite browser in this public list.
>>From: Robert Clary [mailto:bclary@netscape.com] 
>>Example - document.implementation
>>Internet Explorer does not implement the document.implementation 
>>interface of the DOM Core Level 1 specification however the DOM TS 
>>provides a work around which creates test documents via a specific 
>>version of the  MSXML ActiveX control.
>Workarounds are demanded by the DOM spec and IE works according to spec
>as well (on this matter ). Indeed the DOM Level 1 Recommendation
>requires 'createXXX' factory methods to create objects  ( for example
>[1] and [2] ). 
>However, the second paragraph of [2] makes quite clear that creation of
>DOMImplementation and Document objects is not covered; implementers are
>to provide for a proprietary way to create those. This, of course, has
>been mentioned before in this list.
>Perhaps I don't have the background to anticipate the reasons of this
>distinction as decided by the DOM WG but the point is both the Test
>Suite and IE behave ok on this subject.
>[1] "DOM Interfaces and DOM Implementations"  (list item 3)  
>[2] "Memory Management" 
>I hope I will find time to comment on the rest of your post.
>Kindest regards,
Received on Wednesday, 27 February 2002 07:41:15 UTC

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