[TAP5-953] org.apache.tapestry5.dom.Node.remove() should set nextSibling to null

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3, 5.2
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Jochen Kemnade
• Created: 15/Dec/09 12:38
• Updated: 16/Nov/11 06:07
• Resolved: 16/Nov/11 04:44

Description

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.