This is normal, if you replace the part of page using wicket ajax, it will generate the markup and won't preserve your changes. You can either not replace the affected parts of page, or notify server and generate markup with the image.
-Matej On 9/25/07, Michael Preiss <[EMAIL PROTECTED]> wrote: > > I have added some DOM manipulating javascript to my wicket app, that > amongst other things inserts images at the mouse coordinates. The > problem is: after updating a component via wicket, the whole changes > to the DOM will get lost. Any ideas how to solve the problem or work > around it? > > PS: I'm using wicket 1.3 beta 2 > -- > View this message in context: > http://www.nabble.com/DOM-changes-via-JavaScript-get-lost-tf4515396.html#a12879083 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
