You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Werner Punz (JIRA)" <de...@myfaces.apache.org> on 2010/08/04 22:08:17 UTC

[jira] Commented: (MYFACES-2859) Replacing elements for ajax response changes element order

    [ https://issues.apache.org/jira/browse/MYFACES-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895395#action_12895395 ] 

Werner Punz commented on MYFACES-2859:
--------------------------------------

yes the patch looks correct, I had a similar issue a while ago where i was calling a sibling element of an detached node, I dont think it has any sideffects.


> Replacing elements for ajax response changes element order
> ----------------------------------------------------------
>
>                 Key: MYFACES-2859
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2859
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.1, 2.0.2-SNAPSHOT
>            Reporter: Michael Kurz
>         Attachments: MYFACES-2859-test-webapp.zip, MYFACES-2859.patch
>
>
> In my application processing the ajax response for a ajax request changes the order of the elements. I have an html input element with siblings in a div that is replaced with a script and the new input element in the ajax response. The problem is, that the new input element is inserted after the siblings of the original element thus reversing the order of the elements
> I think the problem is in the replaceElements function in _Dom.js. There, oldNode.nextSibling always returns null.
> I created a patch that solves this issue, but I am not sure if there are any side effects. Master of Ajax (Werner) please have a look.

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