Nested element constructors cause loss of namespace bindings

[Federico Cavalieri]

Consider this query:
element {QName("http://outer","bind")}
{
    element {QName("","b")}
    {
        "inner"
    }
}
In zorba and all other libraries it creates as expected:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://outer"><b xmlns="">inner</b></bind>
Notice that b contains xmlns=""

Consider this query now:
element {QName("http://outer","bind")}
{
  element {QName("http://named","named:middle")}
  {
    element {QName("","b")}
    {
      "inner"
    }
  }
}

This one in zorba creates:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://outer"><named:middle xmlns:named="http://named"><b>inner</b></named:middle></bind>
Notice that b inherits xmlns="http://outer"

I would expect the result that is given by Saxon and BaseX:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://outer">
   <named:middle xmlns:named="http://named">
      <b xmlns="">inner</b>
   </named:middle>
</bind>
Notice that b contains xmlns=""

[Matthias Brantner (matthias-brantner)]

fixed in rev. 11986