You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Daniele Dellafiore <il...@gmail.com> on 2008/11/27 10:56:06 UTC
javascript conflicts
Hi all.
I am using wicket-animator and I have discovered today a conflict with
the wicket default component update via ajax.
If a single component is added to the AjaxRequestTarget and I append a
custom javascript via AjaxRequestTarget.appendJavascript() that affect
the same component, i.e. calling a animator.js function, the animation
does not start but the component is refreshed via the wicket standard
mechanism.
The order is: first I call addComponent and after the appendJavascript.
What I would like is that the component get the update and then my
custom javascript runs.
Any advice?
--
Daniele Dellafiore
http://blog.ildella.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org