WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
106531
XMLSerializer's handling of namespaces seems to be pretty broken
https://bugs.webkit.org/show_bug.cgi?id=106531
Summary
XMLSerializer's handling of namespaces seems to be pretty broken
Boris Zbarsky
Reported
2013-01-09 23:21:58 PST
Created
attachment 182074
[details]
Testcase I have yet to find a testcase that actually works correctly, but as a start attached is a simple one that goes wrong. In that testcase, a node with a null namespace is serialized but if the serialization were then parsed again that node would end up in a non-null namespace. I assume that this is not identical to
bug 16496
, since I'm using an XML document created via document.implementation....
Attachments
Testcase
(341 bytes, text/html)
2013-01-09 23:21 PST
,
Boris Zbarsky
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Rob Buis
Comment 1
2013-07-15 19:09:01 PDT
(In reply to
comment #0
)
> Created an attachment (id=182074) [details] > Testcase > > I have yet to find a testcase that actually works correctly, but as a start attached is a simple one that goes wrong. In that testcase, a node with a null namespace is serialized but if the serialization were then parsed again that node would end up in a non-null namespace. > > I assume that this is not identical to
bug 16496
, since I'm using an XML document created via document.implementation....
Bug 16739
patch now contains a fix for the attached testcase.
Rob Buis
Comment 2
2013-07-30 19:00:18 PDT
Committed
r153508
: <
http://trac.webkit.org/changeset/153508
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug