Committed at https://scm.ops4j.org/repos/ops4j/laboratory/users/efy/wicket-contrib-scriptaculous
The examples can be found at https://scm.ops4j.org/repos/ops4j/laboratory/users/efy/wicket-contrib-scriptaculous-examples. Regards, Edward Yakop Note: The wicket dependency version is now set to 1.3.1 On Feb 1, 2008 11:59 PM, Edward Yakop <[EMAIL PROTECTED]> wrote: > On Feb 1, 2008 11:47 PM, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > On Feb 1, 2008 3:26 AM, Lan Boon Ping <[EMAIL PROTECTED]> wrote: > > > My colleague (Edward Yakop) found out the cause root and have a > > > solution for it. The reason why this is only occured in IE is because > > > wicket-ajax.js uses Element.removeChild and Element.addChild to > > > replace component during ajax callback. > > > > Is this an issue with all wicket ajax requests on IE, or just with > > scriptaculous projects? > I believe this is a combination. > Scriptaculous cached the element when "Droppables.add" and "new > Draggable" is invoked and > Wicket ajax behavior handling AjaxRequestTarget#addComponent( ), where > it remove the old element and add > the new element during ajax response. > > Regards, > Edward Yakop > Note: OPS4j server is just backed up, so I haven't have time to update > the code yet. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
