org.apache.tapestry5.dom.Node.remove() should set nextSibling to null
---------------------------------------------------------------------

                 Key: TAP5-953
                 URL: https://issues.apache.org/jira/browse/TAP5-953
             Project: Tapestry 5
          Issue Type: Wish
          Components: tapestry-core
    Affects Versions: 5.1.0.6
            Reporter: Jochen Kemnade


When removing a node from the DOM, its next sibling node should be reset.
This is especially important for the 
moveToBottom(org.apache.tapestry5.dom.Element element) method. The current 
behavior of n.moveToBottom(e) results in n's following siblings being rendered 
twice, once in their original position and once after the moved node. Only the 
latter seems correct to me.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to