You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2008/04/04 15:11:24 UTC

[jira] Assigned: (WICKET-1479) Speed improvement in Ajax re-rendering

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

Johan Compagner reassigned WICKET-1479:
---------------------------------------

    Assignee: Matej Knopp

> Speed improvement in Ajax re-rendering
> --------------------------------------
>
>                 Key: WICKET-1479
>                 URL: https://issues.apache.org/jira/browse/WICKET-1479
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.2
>         Environment: Any
>            Reporter: Martin Grigorov
>            Assignee: Matej Knopp
>            Priority: Minor
>
> According to http://www.quirksmode.org/dom/innerhtml.html replacing HTML fragments with DOM methods is slower than replacing them using .innerHTML.
> wicket-ajax.js, Wicket.Ajax.Call.processComponent calls Wicket.replaceOuterHtml which actually uses DOM for node substitutions.
> Is there any specific reason to use DOM methods ? Or this could be improved ?

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