Erik Dahlström wrote: > If during parsing a 'script' element is encountered, it must not be > executed at that time. Script execution is deferred until the returned > Document (or applicable parts thereof) is inserted into the contextDoc > document. A Document can't be inserted anywhere. Presumably you mean that script execution is deferred until the 'script' element is inserted into the contextDoc document? > If the contextDoc parameter is defined I'm not sure what "defined" means here. The real distinction is whether it's null or not, right? Why not just say that? > provided Document object. In effect when the contextDoc parameter is > specified Again, "not null" is probably better than "specified", since it can be specified to be null. > NOT_SUPPORTED_ERR: Raised if the type of node being imported is > not supported. "imported"? What does that mean? > DOMException > INVALID_CHARACTER_ERR: Raised if one of the imported names is > not an XML name according to the XML version in use specified in the > Document.xmlVersion attribute. This may happen when importing an XML 1.1 > [XML 1.1] element into an XML 1.0 document, for instance." Same here. It looks like these exceptions were copied from the importNode definition in DOM 3 Core; the descriptions make no sense in this context, though. -BorisReceived on Tuesday, 18 July 2006 16:16:29 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 September 2006 18:11:52 GMT