[Bug 28720] Interop: browsers already handle duplicate "fake" xmlns declarations during XML serialization

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28720

--- Comment #7 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Boris Zbarsky from comment #6)
> > under the assumption that if it is needed it will be re-generated in a child
> > element
> 
> For what it's worth, the Gecko behavior is premised on the assumption that
> if you have a default namespace declaration (or indeed any namespace
> declaration) then it should stay in place (since chances are descendants use
> it, and getting rid of it will lead to a huge proliferation of xmlns
> attributes down the tree.  So we do the minimal possible fixup within that
> constraint of just generating a prefix and namespace declaration for the one
> element in question....
> 
> Maybe this doesn't matter too much if there are no practical cases in which
> an element has a default namespace different from its own.

Yes, I suspect that in cases where this might happen, the element in question
has already been moved around in the DOM from its original parsed-position.
Thus assumptions about which namespaces would more naturally apply to the
element or its children are hard to predict.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 29 May 2015 22:06:14 UTC