- From: Charles F Wiecha <wiecha@us.ibm.com>
- Date: Wed, 16 Dec 2009 17:07:38 -0500
- To: Joern Turner <joern.turner@googlemail.com>
- Cc: public-forms@w3.org
- Message-ID: <OF1BD507CC.5C6945C4-ON8525768E.00793479-8525768E.00798C32@us.ibm.com>
Hi Joern -- Firefox is not so picky so I'm not sure if this version has been updated as you suggest. There's now a namespace declaration on the instance (and an extra one for good measure on the root document though probably not needed there...). Lacking any comments to the contrary, we'll include this in the updated test suite zip file shortly. Thanks, Charlie Wiecha (See attached file: 5.1.a.xhtml) Charles Wiecha Multichannel Web Interaction IBM T.J. Watson Research Center P.O. Box 704 Yorktown Heights, N.Y. 10598 Phone: (914) 784-6180, T/L 863-6180, Cell: (914) 282-3483 wiecha@us.ibm.com From: Joern Turner <joern.turner@googlemail.com> To: public-forms@w3.org Date: 12/07/2009 06:33 AM Subject: regarding Testcase 5.1.a Sent by: public-forms-request@w3.org When activating the 'Valid Values' trigger our Validator (Xerces) complains about the Node bound to QName as there's no namespace defined for 'my:myelement' and therefore the prefix 'my' cannot be resolved. The Node becomes invalid. Declaring a namespace with that prefix fixes that problem in our implementation. I think Xerces is right here as the QName validation does not only test for lexical correctness of the QName but also checks if there a namespace in scope for the given prefix. Regards, Joern
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: ecblank.gif
- application/octet-stream attachment: 5.1.a.xhtml
Received on Wednesday, 16 December 2009 22:08:26 UTC