[
https://issues.apache.org/jira/browse/WICKET-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585904#action_12585904
]
Matej Knopp commented on WICKET-1479:
-------------------------------------
Wicket.replaceOuterHtml does *much* more than a simple innerHTML change. It
makes sure that tbody/tr/thead etc are properly replaced (which doesn't work in
IE with innerHTML). And it also takes care of executing embedded <script> tag,
which is normally very inconsistent amongst browsers.
Also I think the benchmark tests generating elements after element using dom
method, which is something different then what we do.
> 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: Igor Vaynberg
> 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.
