Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-953

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

    Details

    • Type: Wish
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.3, 5.2
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      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.

        Attachments

        1. ASF.LICENSE.NOT.GRANTED--nodetest.zip
          8 kB
          Jochen Kemnade
        2. Node.java.patch
          0.2 kB
          Jochen Kemnade

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              jkemnade Jochen Kemnade
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: