Lan Boon Ping wrote:
Hi Nino,
On Jan 28, 2008 10:31 PM, Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED]> wrote:
Without knowing any details at all. Could it have something todo with
wicketAjaxGet, not that the wicketAjaxGet fails but that it's setup
wrongly from scriptaulous?
Not really sure about this. Could you give more information about how
could wicketAjaxGet being setup wrongly?
I was taking a wild guess:) I've looked at it a bit now.. And one thing
that I can see are this line in draggable.js:
Element.makePositioned(element); // fix IE
There are other comment about browsers aswell..
Have you tried debbuging it?
(http://blogs.msdn.com/ie/archive/2007/06/22/from-microsoft-teched-2007-web-development-tools-for-internet-explorer.aspx).
Does it give an actual error message? And where does it fail if so?
Looking at the internals it looks like wicketAjaxGet encapsules a new
method inorder to support backwards compability or something along these
lines.
Are you referring to DraggableTarget.onRender() method? Or something
else? If you were referring to DraggableTarget.onRender(), I didn't
see wicketAjaxGet has encapsulated a new method, it seems nothing
wrong there.
Thanks for your help.
Regards
Boon Ping.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
