Julian Reschke wrote:
For this one I used Dom L1 methods to create this document:
foox:y//foo
which isn't XMLNS-wellformed.
I'm not sure I see the problem here, to be honest... Using the
non-namespace-aware DOM methods one can indeed create documents that require a
non-namespace-aware
Julian Reschke wrote:
Since the UA has no idea what sort of XML parser is being used on the
server side, I'm not sure it makes sense to bail on attempts to
serialize such documents. In particular, if the document _is_ parsed
with a non-namespace-aware XML parser, there is no problem.
Boris Zbarsky wrote:
Julian Reschke wrote:
Since the UA has no idea what sort of XML parser is being used on the
server side, I'm not sure it makes sense to bail on attempts to
serialize such documents. In particular, if the document _is_ parsed
with a non-namespace-aware XML parser, there
Bjoern Hoehrmann wrote:
Being able to send wf-but-ns-illformed documents would not make much
sense if you couldn't also read them back in
Which you can, with a non-NS-aware XML parser.
and the odds that some
wf-but-ns-illformed has been created deliberately for use with XHR
as opposed to
* Boris Zbarsky wrote:
Bjoern Hoehrmann wrote:
Being able to send wf-but-ns-illformed documents would not make much
sense if you couldn't also read them back in
Which you can, with a non-NS-aware XML parser.
My point was that the XHR draft currently requires using a namespace-
aware one, so
