Hi Bernard, Thanks for your comments. I'm not 100% sure this is the same as 4996 but one thing is clear: after an AJAX update of the page Droppables stop to work. On the other hand it seems Stefan was able to fix this patching jquery for issue 4996 so it must be the same issue. Somehow it is clear o me that the problem is that they are holding references to object that do not exists and this is producing exception on IE. Patching jquery myself do not seem to be an option, not in the long run, because then I''l have to take car of testing this local fix on future versions of jquery. So, probably I'll file a new issue and attach what I have to reproduce it (a small Wicket test application).
Thanks again, Ernesto On Tue, Mar 9, 2010 at 8:46 AM, <[email protected]> wrote: > Ernesto, > > Possibly not enough. I would create a testcase as a web page with no > reference to Wicket as a start. > > It is good to avoid any technical distraction because any distraction > causes friction and loss of energy. > > You can of course mention that you are a Wicket developer, and give > some context to support your case, even mentioning that this is being > discussed in this group. > > If you are 100% sure that your scenario is the same as in 4996, then I > would attach the testcase to that ticket. Otherwise I would open a new > one, without any reference to the old one. > > If you are sure about the previous code snippet being not much > different from your attached testcase, then why not mention it, > pointing out that you are just trying to be helpful. You can then ask > what else they need to avoid any further delays. > > In case it is the same issue then I would subscribe to the jQuery dev > mailing list (not user mailing list) and notify them that you are > trying to re-start the issue ... > > Technically, the issue surprises me from this perspective: > > jQuery is fault tolerant in a way that if you run a query that returns > an empty jQuery object and call methods on that empty object, then the > query does not fail. In this case however it fails. I would try to > emphasize this point if possible, concluding that this is in conflict > with jQuery's own apparent design principles. > > Regards, > > Bernard > > > > On Tue, 9 Mar 2010 07:24:39 +0100, you wrote: > > > Do you think would it be "enough" if I provide a wicket quick-start and > >instructions on how to get it running and so on? It would be very easy to > >create one reproducing the issue on a D&D scenario. Or create a new > issues > >and link it to the 4996? > > > >Ernesto > > > >On Mon, Mar 8, 2010 at 9:54 PM, <[email protected]> wrote: > > > >> I don't know, in the header I read: "Needs: Test Case" > >> The bug still has status "new", neither confirmed nor assigned. > >> > >> I am referring to http://dev.jquery.com/ticket/4996 > >> > >> What am I missing? They might need a complete standalone page, > >> preferably zipped that loads jquery.js from the web and displays an > >> error message. You might get some progress if you do that. At least > >> you put the ball back into their court. I did this more than once but > >> it did not help. Nevertheless at least I know what to expect. > >> > >> The outcome could be that a bug needs to be filed against IE. But most > >> importantly the bug needs to be fixed in jQuery because jQuery is > >> crosss-platform and jQuery's existence is based on eliminating these > >> quirks. > >> > >> > >> On Mon, 8 Mar 2010 20:44:22 +0100, you wrote: > >> > >> >Hi Bernard, > >> > > >> >there is a "testcase" in the attachments: > >> > > >> > $(document.createElement('div')).offset(); > >> > > >> >It's a real simple testcase. > >> > > >> >Stefan > >> > > >> >-----Ursprüngliche Nachricht----- > >> >Von: [email protected] [mailto:[email protected]] > >> >Gesendet: Montag, 8. März 2010 20:23 > >> >An: [email protected] > >> >Betreff: Re: jWicket release 0.5.0 > >> > > >> >Thanks for the link to the issue. > >> > > >> >Re: "I don't know why they don't fix the problem." > >> > > >> >I think the jQuery developer asks for a testcase. No testcase was > >> >supplied, so I am not surprised that even after 7 months, nothing has > >> >been done. > >> > > >> >But when there is a testcase, and when even the offending line of code > >> >is identified in jQuery and it is clear that it is a jQuery bug then > >> >the author of jQuery likes to close issues with status WONTFIX > >> >apparently with the purpose to hide them from the community. Please > >> >refer to > >> > > >> >http://dev.jquery.com/ticket/5743 where jQuery updates the DOM during > >> >a call that is supposed to only get the dimensions of an element. > >> > > >> >Regards > >> > > >> >Bernard > >> > > >> > > >> >On Mon, 8 Mar 2010 19:17:54 +0100, you wrote: > >> > > >> >>Hi Ernesto, > >> >> > >> >>yes, I added a patch to jquery1.4.2.js. The D&D problem is relatet to > the > >> ticket you cited (4996). After a DOM replacement IE is unable to > calculate > >> it's bounding rect in the way jQuery does and IE then throws an > exception > >> that stops the re-registration of the behavior. > >> >>The problem seems to be present since jQuery 1.3 and many related bus > are > >> open in jQuery's trac. I don't know why they don't fix the problem. > >> >>So I put together some hints and proposals and modified jQuery.js. If > you > >> need the patch try to check it out from wickststuff trunk or contect me > >> again. > >> >> > >> >>Good luck! > >> >>Stefan > >> >> > >> >>-----Ursprüngliche Nachricht----- > >> >>Von: Ernesto Reinaldo Barreiro [mailto:[email protected]] > >> >>Gesendet: Montag, 8. März 2010 19:07 > >> >>An: [email protected] > >> >>Betreff: Re: jWicket release 0.5.0 > >> >> > >> >>Hi Stefan, > >> >> > >> >>My I ask what was your solution to the D&D problem? Added a patch to > >> jquery? > >> >>Was this related to [1] and using jquery 1.4.2, independently of your > >> >>project, and still find this issue. > >> >> > >> >>Best, > >> >> > >> >>Ernesto > >> >> > >> >>References, > >> >> > >> >>1-http://dev.jquery.com/ticket/4996 > >> >> > >> >><http://dev.jquery.com/ticket/4996> > >> >> > >> >>On Fri, Feb 26, 2010 at 2:57 PM, Stefan Lindner <[email protected]> > >> wrote: > >> >> > >> >>> I have committed jWicket version 0.5.0 to wicketstuff > >> >>> > >> >>> Changes: > >> >>> - jQuery update to Version 1.4.2 > >> >>> - jQuery UI update to 1.8RC2 > >> >>> - drag/drop/resize improvements to work in IE 6/7/8 after AJAX > update > >> or > >> >>> in LazyLoad panels > >> >>> - drag/drop/resize improvements for less footprint in HTML, smaller > js > >> >>> code generation > >> >>> - Effects rewritten completely, now covering all effects > >> >>> - Effects now support a chain of multiple effects > >> >>> > >> >>> Known Issues > >> >>> - Example application not very attractive > >> >>> - Example applicatioin contains some debugging code > >> >>> > >> >>> Let me know if someone needs prebuild jar files. > >> >>> > >> >>> Stefan > >> >>> > >> >>> > --------------------------------------------------------------------- > >> >>> 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] > >> > >> > >> --------------------------------------------------------------------- > >> 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] > >
