Search and Top Navigation
#5890 closed bug (duplicate)
Opened July 31, 2010 02:15PM UTC
Closed March 08, 2013 03:51AM UTC
Last modified March 08, 2013 03:57AM UTC
Sortable:sortout fires on sortstart and sortstop too
Reported by: | Peter007 | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 2.0.0 |
Component: | ui.sortable | Version: | 1.8.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Working example http://jsfiddle.net/FrbW8/22/
Can your fix this bug?
Thanx for help.
Kind regards
Peter (germany)
Attachments (0)
Change History (4)
Changed October 11, 2012 09:07PM UTC by comment:1
milestone: | TBD → 2.0.0 |
---|
Changed November 03, 2012 07:21PM UTC by comment:2
status: | new → open |
---|---|
summary: | SortOut: fires on sortstart and sortstop too → Sortable:sortout fires on sortstart and sortstop too |
The docs say that the out event is triggered when a sortable item is moved away from a connected list. Yet it its firing even when the sortable doesn't have a connected list. Which is right the code or the docs?
Changed March 08, 2013 03:51AM UTC by comment:3
resolution: | → duplicate |
---|---|
status: | open → closed |
Duplicate of #8669.I'm not seeing the out fired on start, and the firing on stop is intended and has since been documented as such (see #8669).
See petersendidit's comments I will change the API documentation to remove the word "connected" from the out and over events since they occur on all sortable lists.