Skip to main content

Search and Top Navigation

#4239 closed bug (fixed)

Opened February 26, 2009 12:50PM UTC

Closed August 22, 2009 07:22AM UTC

Last modified April 18, 2013 01:44AM UTC

Cannot destroy draggable functionality after drop

Reported by: bobbykjack Owned by:
Priority: minor Milestone: 1.8
Component: ui.draggable Version: 1.6rc6
Keywords: Cc:
Blocked by: Blocking:
Description

This is very similar to #4088 and #4087 except that I'm trying to destroy the draggable functionality once it's been dropped, not destroy the entire element. At that method call, I currently get this error:

$(this).data("draggable") is undefined
var o = $(this).data('draggable').options;
ui.draggable.js (line 583)

I'm attaching two files to demo the problem and a workaround (whose side-effects I'm not too clear on).

Attachments (2)
  • jquery-draggable-bug-workaround.html (1.3 KB) - added by bobbykjack February 26, 2009 12:51PM UTC.

    Test case for disabling draggable functionality after drop

  • jquery-draggable-bug.html (1.3 KB) - added by bobbykjack February 26, 2009 12:50PM UTC.

    Test case for destroying draggable functionality after drop

Change History (5)

Changed February 27, 2009 07:28PM UTC by jzaefferer comment:1

milestone: TBD1.7

Changed March 08, 2009 02:35PM UTC by rdworth comment:2

milestone: 1.71.8

Changed August 22, 2009 07:22AM UTC by paul comment:3

resolution: → fixed
status: newclosed

Should be fixed with r3103.

Changed April 17, 2013 09:16AM UTC by usiw comment:4

This problem still exists in 1.10.2. Either the original fix was reverted or it was never resolved to begin with.

Changed April 18, 2013 01:44AM UTC by tj.vantoll comment:5

Replying to [comment:4 usiw]:

This problem still exists in 1.10.2. Either the original fix was reverted or it was never resolved to begin with.

The test case originally created with this issue appears to be working just fine against the latest code in master: http://jsfiddle.net/tj_vantoll/7huH8/. If you have an issue that you would like us to look into we'll need a test case that shows the issue.