http://www.commoner.com/~lsimon/scriptaculous/test/functional/dragdrop7_test.html
In IE, if you click on the "Reload cart droppable via ajax", and then try to move the draggable, it goes kablaam. Notice too that if you reload and try to click Remove Droppable that the # of droppables stays at 1 or whatever, instead of going back to 0. The DOM comparison in Droppables.remove doesn't work when you do an AJAX update of the content containing the droppable. The element.id stays the same, but the element==element part resolves to false. Should we use element.id==element.id comparison to solve this? Does an Updater replacing an element with an element of the same dom id somehow violate a best practice notion? My use case of this issue is that I have an editor xhtml template that loads when you click on an item to edit - the template is loaded via Ajax.Updater but whenever you reload one, the sortables break because of this, but maybe I should be changing all the ID's every time? Bug #2409 was this problem originally I believe. -- Lindsey Simon [EMAIL PROTECTED] Key fingerprint = C6A9 B9D9 677E A631 3E7F 43BF 5E2F 77F1 A33C B117 Public Key: http://www.commoner.com/pubkey.asc _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
