Hi Scott and thanks for your reply! I had initially given up on this, but your reply made me give it even some more effort to the issue. Turns out i've been a total moron when "duplicating" the original input-element -> to a new anchor-element. I duplicated the ID as well. So the onclick was triggered it turns out, but wicket didn't do anything about it because it halted on behalf of 2 target elements instead of 1 unique.
Totaly my bad, but perhaps someone will come in a similar situation one day and learn from my stupid mistake :) On 22 Mai, 17:13, Scott Sauyet <[EMAIL PROTECTED]> wrote: > One thought. Are you absolutely certain that "prev()" is returning the > correct element? If you are manipulating the DOM at all, you need to > check this not only in the original Wicket markup, in the generated HTML > document, and in Firebug or some tool that shows the dynamic DOM.
