Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Message-ID: <82577960.1260880878227.JavaMail.jira@brutus>
Date: Tue, 15 Dec 2009 12:41:18 +0000 (UTC)
From: "Jochen Kemnade (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Subject: [jira] Updated: (TAP5-953) org.apache.tapestry5.dom.Node.remove()
 should set nextSibling to null
In-Reply-To: <460193564.1260880758304.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAP5-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-953:
--------------------------------

    Attachment: Node.java.patch

> 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
>         Attachments: Node.java.patch
>
>
> 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.