Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
No, i haven't yet. the problem for me is that I don't have an install
of IE6/7 to test this out on. I'd be happy to apply any patch that
someone has that has been tested against IE6 and IE7 though.
On Feb 13, 2008 12:54 AM, Edward Yakop [EMAIL PROTECTED] wrote:
Hi,
Thanx for the hints :)
The problem is solved, but I'm not sure whether Ryan has patched the
scriptaculous code in wicket-stuff svn.
Regards,
Edward Yakop
On Feb 13, 2008 2:10 PM, Ernesto Reinaldo Barreiro [EMAIL PROTECTED] wrote:
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
-
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Ok everyone, I think I have a fix checked in. Before re-rendering the
DraggableTarget on the Ajax response, I call the scriptaculous
Droppables.remove() to cleanup the old reference.
The wicketstuff-scriptaculous-example project should be able to test
and verify this behavior. If anyone has a spare browser that they can
throw at it to see that it works, I'd appreciate it.
Thank you *everyone* for your contributions. I never would have
noticed this issue without your help!
On Feb 13, 2008 10:39 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
if you have an example running, i'll be happy to test on safari and
ie6/7/ff ..
Ryan Sonnek wrote:
No, i haven't yet. the problem for me is that I don't have an install
of IE6/7 to test this out on. I'd be happy to apply any patch that
someone has that has been tested against IE6 and IE7 though.
On Feb 13, 2008 12:54 AM, Edward Yakop [EMAIL PROTECTED] wrote:
Hi,
Thanx for the hints :)
The problem is solved, but I'm not sure whether Ryan has patched the
scriptaculous code in wicket-stuff svn.
Regards,
Edward Yakop
On Feb 13, 2008 2:10 PM, Ernesto Reinaldo Barreiro [EMAIL PROTECTED]
wrote:
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
-
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]
--
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
if you have an example running, i'll be happy to test on safari and
ie6/7/ff ..
Ryan Sonnek wrote:
No, i haven't yet. the problem for me is that I don't have an install
of IE6/7 to test this out on. I'd be happy to apply any patch that
someone has that has been tested against IE6 and IE7 though.
On Feb 13, 2008 12:54 AM, Edward Yakop [EMAIL PROTECTED] wrote:
Hi,
Thanx for the hints :)
The problem is solved, but I'm not sure whether Ryan has patched the
scriptaculous code in wicket-stuff svn.
Regards,
Edward Yakop
On Feb 13, 2008 2:10 PM, Ernesto Reinaldo Barreiro [EMAIL PROTECTED] wrote:
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
-
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]
--
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
The reason why this might not work is when we have the following use case:
* We have many draggable target, and when somebody drop to one of the
location, containers that contained the other draggable targets are
also added to ajax request target. Once this happened, none of the
other draggable targets will work.
* The same thing also applies to Droppables, if the container of
droppables are added to the AjaxRequestTarget. These droppables will
no longer work too.
The way that this is fixed at my project is by forcing the user to use
my ajax request target.
I have a hook to ajax request target to listen when components are
added to ajax request target, and do necessary callback to allow the
behaviors to do something. In my case, usually called
Droppables.remove( $( markupId ) ), and for Draggables, since there's
no easy way to potentially need to re-initialize some but not all, I
have to iterate the Draggables.drag array and inovoke
Draggable#destroy.
I would think there probably a better way to handle this without
subclassing AjaxRequestTarget. Will come back to this later.
Regards,
Edward Yakop
On Feb 14, 2008 12:53 AM, Ryan Sonnek [EMAIL PROTECTED] wrote:
Ok everyone, I think I have a fix checked in. Before re-rendering the
DraggableTarget on the Ajax response, I call the scriptaculous
Droppables.remove() to cleanup the old reference.
The wicketstuff-scriptaculous-example project should be able to test
and verify this behavior. If anyone has a spare browser that they can
throw at it to see that it works, I'd appreciate it.
Thank you *everyone* for your contributions. I never would have
noticed this issue without your help!
On Feb 13, 2008 10:39 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
if you have an example running, i'll be happy to test on safari and
ie6/7/ff ..
Ryan Sonnek wrote:
No, i haven't yet. the problem for me is that I don't have an install
of IE6/7 to test this out on. I'd be happy to apply any patch that
someone has that has been tested against IE6 and IE7 though.
On Feb 13, 2008 12:54 AM, Edward Yakop [EMAIL PROTECTED] wrote:
Hi,
Thanx for the hints :)
The problem is solved, but I'm not sure whether Ryan has patched the
scriptaculous code in wicket-stuff svn.
Regards,
Edward Yakop
On Feb 13, 2008 2:10 PM, Ernesto Reinaldo Barreiro [EMAIL PROTECTED]
wrote:
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
-
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]
--
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Hi,
Thanx for the hints :)
The problem is solved, but I'm not sure whether Ryan has patched the
scriptaculous code in wicket-stuff svn.
Regards,
Edward Yakop
On Feb 13, 2008 2:10 PM, Ernesto Reinaldo Barreiro [EMAIL PROTECTED] wrote:
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Don't know if it is the same issue but I have found the same problem a
while ago (refreshing a component via Ajax) and the problem was
scriptaculous requires to clean up the Droppables if an element was
removed from the DOM tree. So, all I did was add a a clearAll
(JavaScript) method that delete all the Droppables. something like
var Droppables = {
drops: [],
removeAll: function(element) {
this.drops = [];
},
..
and then call it before any Ajax request that recreated the DOM tree. So
that I could safely recreated my component and make them droppables
again. This worked fine for IE7. For Firefox I never found those
problems... There was a note on the web page explaining Droppables that
suggested this idea...
Hope this helps...
Best,
Ernesto
Lan Boon Ping wrote:
Hi,
I have encountered a DragNDrop problem using wicketStuff-scriptaculous
in IE6/IE7. The DragNDrop only work for the first time, but
subsequently, the draggable object is no longer draggable. FYI, this
problem doesn't exist in Firefox and it can be reproduced in
wicket-contrib-scriptaculous-examples.
Any hints?
Thanks in advance.
Regards
Boon Ping.
-
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Hi Nino,
I was busy yesterday, sorry for being late to reply you.
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.
So, the solution is to add an AjaxRequestTarget.IListener which hook
into Ajax Response cycle and do something in onBeforeRespond() method.
In onBeforeRespond, we will loop up droppable components and invoke
AjaxRequestTarget.prependJavascript( Droppables.remove(' + markupId
+ ');); );
to remove them from Javascript Droppables object and update it
AjaxRequestTarget.add( droppableComponentToBeUpdated );
lastly we invoke this script to add the droppable javascript back to
droppable components.
AjaxRequestTarget.appendJavascript( onDropJavaScript );
FYI, we don't have any patches for wicketstuff-scriptaculous, because
we are using customized version which hosted in OPS4J. Sorry for any
inconvenient.
Anyway, thanks for your offers.
Regards
Boon Ping.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Forgot to mention that Edward will update the customized version in OPS4J soon.
Regards
Boon Ping.
On Feb 1, 2008 5:26 PM, Lan Boon Ping [EMAIL PROTECTED] wrote:
Hi Nino,
I was busy yesterday, sorry for being late to reply you.
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.
So, the solution is to add an AjaxRequestTarget.IListener which hook
into Ajax Response cycle and do something in onBeforeRespond() method.
In onBeforeRespond, we will loop up droppable components and invoke
AjaxRequestTarget.prependJavascript( Droppables.remove(' + markupId
+ ');); );
to remove them from Javascript Droppables object and update it
AjaxRequestTarget.add( droppableComponentToBeUpdated );
lastly we invoke this script to add the droppable javascript back to
droppable components.
AjaxRequestTarget.appendJavascript( onDropJavaScript );
FYI, we don't have any patches for wicketstuff-scriptaculous, because
we are using customized version which hosted in OPS4J. Sorry for any
inconvenient.
Anyway, thanks for your offers.
Regards
Boon Ping.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Ok, maybe Ryan will pickup on this.. As im not that familiar with
scriptaculouls.. Not sure if jira's setup for this project, but if it
is. You could just create a issue and paste a link from nabble?
regards Nino
Lan Boon Ping wrote:
Forgot to mention that Edward will update the customized version in OPS4J soon.
Regards
Boon Ping.
On Feb 1, 2008 5:26 PM, Lan Boon Ping [EMAIL PROTECTED] wrote:
Hi Nino,
I was busy yesterday, sorry for being late to reply you.
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.
So, the solution is to add an AjaxRequestTarget.IListener which hook
into Ajax Response cycle and do something in onBeforeRespond() method.
In onBeforeRespond, we will loop up droppable components and invoke
AjaxRequestTarget.prependJavascript( Droppables.remove(' + markupId
+ ');); );
to remove them from Javascript Droppables object and update it
AjaxRequestTarget.add( droppableComponentToBeUpdated );
lastly we invoke this script to add the droppable javascript back to
droppable components.
AjaxRequestTarget.appendJavascript( onDropJavaScript );
FYI, we don't have any patches for wicketstuff-scriptaculous, because
we are using customized version which hosted in OPS4J. Sorry for any
inconvenient.
Anyway, thanks for your offers.
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Hi Nino,
Good suggestion, I just checked the
site(http://wicketstuff.org/jira/secure/Dashboard.jspa) but couldn't
find wicketstuff-scriptaculous. I guess it is ok, because Ryan is
already aware of it.
Regards
Boon Ping.
On Feb 1, 2008 5:43 PM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Ok, maybe Ryan will pickup on this.. As im not that familiar with
scriptaculouls.. Not sure if jira's setup for this project, but if it
is. You could just create a issue and paste a link from nabble?
regards Nino
Lan Boon Ping wrote:
Forgot to mention that Edward will update the customized version in OPS4J
soon.
Regards
Boon Ping.
On Feb 1, 2008 5:26 PM, Lan Boon Ping [EMAIL PROTECTED] wrote:
Hi Nino,
I was busy yesterday, sorry for being late to reply you.
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.
So, the solution is to add an AjaxRequestTarget.IListener which hook
into Ajax Response cycle and do something in onBeforeRespond() method.
In onBeforeRespond, we will loop up droppable components and invoke
AjaxRequestTarget.prependJavascript( Droppables.remove(' + markupId
+ ');); );
to remove them from Javascript Droppables object and update it
AjaxRequestTarget.add( droppableComponentToBeUpdated );
lastly we invoke this script to add the droppable javascript back to
droppable components.
AjaxRequestTarget.appendJavascript( onDropJavaScript );
FYI, we don't have any patches for wicketstuff-scriptaculous, because
we are using customized version which hosted in OPS4J. Sorry for any
inconvenient.
Anyway, thanks for your offers.
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
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? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
That's quite a shocker to me. if it works in the scriptaculous demo, i don't see why it wouldn't work in wicket. On Jan 29, 2008 9:29 PM, Lan Boon Ping [EMAIL PROTECTED] wrote: Say if you have trouble with it. I'll look into it then, two pair of eyes are better than one:) Hey thats what the mailing list are for:) I learn from this too:) Great! You are welcome! :) FYI, draggable.js seems not the one that cause the problem, because the DnD demo in scriptaculous[1] site works perfectly, I suspect that the problem is from the integration in wicketstuff-scriptaculous. I will take a deeper look today. Btw, if you need more information, please pm me. Thanks a lot. Regards Boon Ping. [1] http://demo.script.aculo.us/shop - 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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
could you send a quickstart to me, or point me to an url so I can debug? regards Nino Lan Boon Ping wrote: Say if you have trouble with it. I'll look into it then, two pair of eyes are better than one:) Hey thats what the mailing list are for:) I learn from this too:) Great! You are welcome! :) FYI, draggable.js seems not the one that cause the problem, because the DnD demo in scriptaculous[1] site works perfectly, I suspect that the problem is from the integration in wicketstuff-scriptaculous. I will take a deeper look today. Btw, if you need more information, please pm me. Thanks a lot. Regards Boon Ping. [1] http://demo.script.aculo.us/shop - 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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Lan Boon Ping wrote: Hi, I didn't have a change to debug it yet, because I don't have a dedicated PC with XP IE6 installed, we are setting up a new one now. I will take a deeper look at it soon. Thanks for the link. On Jan 29, 2008 3:33 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: 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.. I think you are right, this line of code is suspicious of causing the problem. I got this error from browser IE7. Error :'Position' is null or not an object' Code :0 One step closer to it, thanks. Say if you have trouble with it. I'll look into it then, two pair of eyes are better than one:) Hey thats what the mailing list are for:) I learn from this too:) 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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
Say if you have trouble with it. I'll look into it then, two pair of eyes are better than one:) Hey thats what the mailing list are for:) I learn from this too:) Great! You are welcome! :) FYI, draggable.js seems not the one that cause the problem, because the DnD demo in scriptaculous[1] site works perfectly, I suspect that the problem is from the integration in wicketstuff-scriptaculous. I will take a deeper look today. Btw, if you need more information, please pm me. Thanks a lot. Regards Boon Ping. [1] http://demo.script.aculo.us/shop - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
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? Looking at the internals it looks like wicketAjaxGet encapsules a new method inorder to support backwards compability or something along these lines. regards Nino Lan Boon Ping wrote: Hi, I have encountered a DragNDrop problem using wicketStuff-scriptaculous in IE6/IE7. The DragNDrop only work for the first time, but subsequently, the draggable object is no longer draggable. FYI, this problem doesn't exist in Firefox and it can be reproduced in wicket-contrib-scriptaculous-examples. Any hints? Thanks in advance. 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]
Re: [WicketStuff-Scriptaculous] DragNDrop problem in IE6/IE7.
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? 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]
