- From: Bob Foster <bob.foster@webgain.com>
- Date: Fri, 13 Jul 2001 20:04:26 -0500
- To: <www-dom@w3.org>
Won't trying to set nodeValue on an Element also throw? Bob Foster WebGain ----- Original Message ----- From: "Joseph Kesselman" <keshlam@us.ibm.com> To: "David Flanagan" <david@oreilly.com> Cc: <www-dom@w3.org> Sent: Friday, July 13, 2001 5:20 PM Subject: Re: DOMException: NO_MODIFICATION_ALLOWED_ERROR > > 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 > node. > > 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 Saturday, 14 July 2001 03:54:35 UTC