I posted earlier this week about a problem with Interface and the drag/drop/sort functionality. Someone pointed out that my example had an error in IE, so I went back to the drawing board to refactor the code. I've posted three demo pages that explain my problem:
http://beta.bryanbuchs.com/index.html http://beta.bryanbuchs.com/index.html http://beta.bryanbuchs.com/index2.html http://beta.bryanbuchs.com/index2.html http://beta.bryanbuchs.com/index3.html http://beta.bryanbuchs.com/index3.html The first link demonstrates that my code isn't entirely wonky - draggables and droppables are working fine. In the second example, all I did was to include the "isortables" file, and everything goes haywire. In the last example, I actually create a sortable list; this stops one error from occuring, but introduces functionality that I think is just wrong. Stefan, I hope you're reading and can take a look at my examples. As I mentioned in my last post, I believe the problems stem from the Sept. 11 2006 modifications that were made; the big update was that a droppable dropped in a sortable becomes part of the sortable. In my opinion, a draggable is a draggable, a droppable is a droppable, and a sortable is a sortable. if you want to convert an element from one to the other, it should not happen automatically. If it's an option that can be passed, that's fine, but it should not be the default behaviour. I think my examples show why the auto-conversion is a bad idea. -- View this message in context: http://www.nabble.com/Interface%3A-draggables%2C-droppables%2C-and-sortables-tf2280438.html#a6334800 Sent from the JQuery forum at Nabble.com. _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
