W3C home > Mailing lists > Public > www-svg@w3.org > July 2006

RE: [SVGMobile12] parseXML method needs clarification

From: Andrew Emmons <aemmons@opentext.com>
Date: Thu, 20 Jul 2006 13:48:37 -0400
Message-ID: <BEF1FB69553AF14BBC63700F25699A13056D3742@OTWATMX01.opentext.net>
To: "Boris Zbarsky" <bzbarsky@mit.edu>, Erik Dahlström <ed@opera.com>
Cc: <www-svg@w3.org>


*Boris Zbarsky wrote:
 
> >         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.
> 
> -Boris
> 

Thank you very much for your feedback. We have clarified these exceptions in the context of parseXML:

DOMException  NOT_SUPPORTED_ERR: Raised if the XML contains unsupported node types.  
DOMException  INVALID_CHARACTER_ERR: Raised if one of the parsed XML names is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute of the contextDoc.  


All the best,
Andrew Emmons, on behalf of the SVG Working Group
Received on Thursday, 20 July 2006 17:49:08 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:35 GMT