Remember Wicket.Ajax.ajax bindings after altering DOM with javascript.

Hi I'm in the process of updating a wicket application from wicket 1.5 to wicket 6, and have come across a challenge regarding third party javascript code altering the DOM after markup has been sent to the client. Basically there are several elements in the markup who are distributed evenly acro

Re: Remember Wicket.Ajax.ajax bindings after altering DOM with javascript.

Using clone(true, true) solved it! Thank you for your fast response :-) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Remember-Wicket-Ajax-ajax-bindings-after-altering-DOM-with-javascript-tp4666091p4666095.html Sent from the Users forum mailing list archive at Nabble

Help request regarding simple DefaultNestedTree implementation

Hi guys, I'm having trouble implementing the AdvancedTreePage-example from Wicket Examples. As the example is equipped with a dropdown to choose from different content presentations and a dropdown to choose from different themes, I'm trying to simplify the example into my own implementation using

Re: Help request regarding simple DefaultNestedTree implementation

The solution was to disable page specific styling of fonts. Seems that using a different font (inherited from master page) was causing the B folder to appear as shifted to the right. When using font-family:inherit, this visual presentation is now correct. -- View this message in context: http://a