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


From: Joseph Kesselman <keshlam@us.ibm.com>
Date: Fri, 13 Jul 2001 18:20:02 -0400
To: David Flanagan <david@oreilly.com>
Cc: www-dom@w3.org
Message-ID: <OF86E640CD.5B79C721-ON85256A88.007A0727@pok.ibm.com>

See recent discussion in the archives of this mailing list: Descendents of
an Entity andEntityReference nodes and their descendents are read-only. So
are Notation nodes (The DOM's index and glossary pages are useful for this;
looking in the index found this fairly quickly)

This exception may also be thrown in some cases if the specific operation
is forbidden in this node -- eg, trying to set nodeValue for an Entity

The DOM does not say there aren't any other ways that nodes can become
read-only. We may add APIs to control that in the future. And some DOM
implementations have implementation-specific mechanisms that may cause this
to happen.

Joe Kesselman  / IBM Research
Received on Friday, 13 July 2001 18:20:36 UTC

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