W3C home > Mailing lists > Public > www-dom@w3.org > January to March 1998

Re: Question about getNextSibling/getPreviou

From: Gavin Nicol <gtn@eps.inso.com>
Date: Mon, 9 Mar 1998 16:16:25 GMT
Message-Id: <199803091616.QAA01616@nathaniel.eps.inso.com>
To: akirkpatrick@ims-global.com
CC: www-dom@w3.org
>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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:44 GMT