Re: Component twice in markup while ajax refresh in Wicket 6.7 (migrated from 1.5.10)

2013-05-15 Thread Nico
message will be added to the discussion below: http://apache-wicket.1842946.n4.nabble.com/Component-twice-in-markup-while-ajax-refresh-in-Wicket-6-7-migrated-from-1-5-10-tp4658789p4658791.html To unsubscribe from Component twice in markup while ajax refresh in Wicket 6.7 (migrated from 1.5.10

Component twice in markup while ajax refresh in Wicket 6.7 (migrated from 1.5.10)

2013-05-14 Thread Nico
Hi I migrated my application from Wicket 1.5.10 to 6.7 During testing I recognized that during an ajax update (replacement) of a component, the markup of the component is twice in the HTML markup (the old and the new markup). Thus the execution of javascript inside a component may fail due to

Re: Component twice in markup while ajax refresh in Wicket 6.7 (migrated from 1.5.10)

2013-05-14 Thread Sven Meier
Create a quickstart and attach it to a Jira issue please. Sven On 05/14/2013 04:37 PM, Nico wrote: Hi I migrated my application from Wicket 1.5.10 to 6.7 During testing I recognized that during an ajax update (replacement) of a component, the markup of the component is twice in the HTML

Re: Component twice in markup while ajax refresh in Wicket 6.7 (migrated from 1.5.10)

2013-05-14 Thread Martin Grigorov
Hi, We use https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js#L1617 because it is faster than jQuery#replaceWith(). So yes, there is a small period when both the old and the new are in the DOM. As Sven asked - please create a