When serializing an element with null namespace within an XHTML document, XMLSerializer should reset the namespace - currently, the result is as if the element were in XHTML namespace, too. Firefox 2 also has this problem.
Created attachment 18285 [details] test case
Created attachment 205404 [details] Patch
Comment on attachment 205404 [details] Patch This is based on bug 16496 patch which is not in yet, so clear the review flag for now.
Created attachment 205439 [details] Patch
Created attachment 205491 [details] Patch
Created attachment 205634 [details] Patch
Comment on attachment 205634 [details] Patch Clearing review flag because it builds on the patch in bug 16496. Compared to the previous patch this now includes the missing MarkupAccumulator.h change.
Created attachment 206717 [details] Patch
Created attachment 206894 [details] Patch
Comment on attachment 206894 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=206894&action=review > Source/WebCore/editing/MarkupAccumulator.cpp:303 > + result.append(xmlnsAtom.string()); Maybe we should probably add a version of append that takes AtomicString. > Source/WebCore/editing/MarkupAccumulator.cpp:306 > + result.append('='); > + result.append('"'); > + result.append('"'); Why can't we just do result.appendLiteral("=\"\"");? > LayoutTests/fast/dom/XMLSerializer-element-empty-namespace-expected.txt:2 > +<div xmlns="http://www.w3.org/1999/xhtml" id="target"> <div id="output"> </div><a xmlns="" href="#"/></div> > + It'll be nice if the test had some description on what it's testing. > LayoutTests/fast/dom/XMLSerializer-element-empty-namespace2-expected.txt:1 > +<x xmlns="foo"><y xmlns=""/></x> Ditto.
Committed r153508: <http://trac.webkit.org/changeset/153508>
Mass moving XML DOM bugs to the "DOM" Component.