tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-953) org.apache.tapestry5.dom.Node.remove() should set nextSibling to null
Date Mon, 15 Nov 2010 10:24:15 GMT

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

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

    Affects Version/s: 5.2.3

> 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.2.0, 5.2.1, 5.2.2, 5.2.3, 5.1.0.6, 5.1.0.7
>            Reporter: Jochen Kemnade
>         Attachments: Node.java.patch, nodetest.zip
>
>
> 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.


Mime
View raw message