W3C home > Mailing lists > Public > www-dom@w3.org > July to September 1998

Re: DOM Level 1 doesn't do everything

From: <keshlam@us.ibm.com>
Date: Tue, 28 Jul 1998 17:31:10 -0400
To: www-dom@w3.org
Message-ID: <8525664F.00741495.00@us.ibm.com>
As you say: Next/prevous on Node is functionally _different_ than
next-previous on a ByTagName NodeList. The latter does not currently exist
in the spec; only integer access (with all the associated pain) is

I have confidence that Level 2 will address this. I just wish Level 1
wasn't asking us to implement a substantial chunk of code which we expect
and hope to throw away.

Of course there's always the other approach to resolving the conflict: Is
it Really Necessary that NodeList be "live"? How often is this going to
matter, and is it in fact the behavior you want (as opposed to requesting a
new NodeList when you know that changes have been made that you need to
respond to)?

On a slightly different note, here's a suggestion from a friend: Have you
considered picking up some of the Model/View/Controller ideas and applying
them to the DOM? Specifically, it might make sense to add the ability to
register some flavor(s) of TreeChangeListener, which would be called when
the relevant portion of the document was altered. That will become
especially necessary when you start dealing with multiple access, and
particularly if the integer indices are preserved -- you'll have to know
what happened in order to adjust those appropriately.
Received on Tuesday, 28 July 1998 17:30:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:04 UTC