510107 - E4X: namespace lost and new namespace created when appending a node via operator[]

Status: RESOLVED WONTFIX

(Tamarin Graveyard :: Library, defect)

Description

[Chris Peyer]

Description:

When appending to a node a few levels deep, when each node has a namespace, the namespace ends up being lost and the node hierarchy is replicated to some extent, with the one new node being created having a namespace of "null" (the string n-u-l-l) and another one added as an unqualified element, which would put it in the default namespace if one were present.

Steps to reproduce:

1. Run the following:
var xml:XML =
<ss:Root xmlns:ss="some-ns">
<ss:Depth1>
<ss:Depth2>
<ss:Depth3/>
</ss:Depth2>
</ss:Depth1>
</ss:Root>

var ssNS:Namespace = xml.namespace("some-ns");
default xml namespace = ssNS;

xml.Depth1.Depth2.children()[xml.Depth1.Depth2.children().length()] =
<ss:Child2 xmlns:ss="some-ns"/>;

trace(xml.toXMLString());

Actual Results:

<ss:Root xmlns:ss="some-ns">
  <ss:Depth1>
    <ss:Depth2>
      <ss:Depth3/>
    </ss:Depth2>
  </ss:Depth1>
  <Depth1 xmlns="null">
    <Depth2>
      <ss:Child2/>
    </Depth2>
  </Depth1>
</ss:Root>
 
Expected Results:

<ss:Root xmlns:ss="some-ns">
  <ss:Depth1>
    <ss:Depth2>
      <ss:Depth3/>
      <ss:Child2/>
    </ss:Depth2>
  </ss:Depth1>
 </ss:Root>


This bug transferred from: http://bugs.adobe.com/jira/browse/ASC-3788

Comment 1

[Steven Johnson]

Any fix for this bug will likely need version-checking for backwards compatibility.

Comment 2

[Nicholas Nethercote [inactive]]

e4x support has been removed (bug 788293).