[
https://issues.apache.org/jira/browse/WICKET-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1479.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg (was: Matej Knopp)
there are a couple of reasons why we use outerhtml instead of inner
* tag attributes can be updated, innerhtml doesnt take care of this
* some elements have broken innerhtml support in different browsers -
tbody/tr/etc
* we need to hide the tag itself when visibility changes, that means replacing
the tag with a different one
> 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.
