Re: Question about getNextSibling/getPreviou

>The only way this could be improved is by adding next/previous
>pointers to each node which will a) increase memory use and
>b) make editing the tree very tedious=2E Also, given the current
>DOM, there are no methods for setting the previous/next so this
>approach isn't possible=2E

There are a number of ways of maintaining the nextSibling() and
previousSibling() information. These are *very* useful for many
things, so it was felt wise to incorporate them as standard API's.

Received on Monday, 9 March 1998 11:16:33 UTC