Side navigation
#3059 closed enhancement (invalid)
Opened June 18, 2008 01:05PM UTC
Closed October 03, 2010 12:59AM UTC
Bad positioning of clone delete in ui.sortable.js
Reported by: | supahfly | Owned by: | stefan |
---|---|---|---|
Priority: | critical | Milestone: | 1.3 |
Component: | interface | Version: | 1.2.6 |
Keywords: | Cc: | supahfly | |
Blocked by: | Blocking: |
Description
Hi Guys,
i'm just testing your ui-Enviroment for our social-community www.kwick.de .
We're about to switch from the eyecon-interface to yours, because we use jquery since a year now and its better to have all from one hand :)
In your code in <Revision: $Id: ui.sortable.js 5452 2008-05-05 16:42:08Z rdworth $> I have found out, that in every event-handler (start, stop, change)
the clone-helper <this.helper> is being remove after the callback-functions are executed.
This is not working for us (and I think for many others either), because my callback function saves the layer-positions on stop. Because the clone-layer is still present at this time i made a hotfix for us, so that the callback is called after destroying the clone-layer.
Could you please think about to consider this change in your further patch? Because we would be always up to date with your versions without making our changes in your code by ourselves :)
Thanks so much.
Please mail me your answer on florian.berninger@kwick.de
Greetings and a nice day from Germany
Florian
This belongs to jQuery UI.
Please repost this to the UI Bug Tracker.