Search and Top Navigation
#3980 closed bug (fixed)
Opened January 29, 2009 12:49PM UTC
Closed February 01, 2009 04:37AM UTC
Last modified February 12, 2009 12:00PM UTC
Disabled sortable still receives elements
| Reported by: | Marc Diethelm | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 1.7 |
| Component: | ui.draggable | Version: | 1.6rc5 |
| Keywords: | sortable, disable, disabled, receive, receives | Cc: | boo@chic-happens.ch |
| Blocked by: | Blocking: |
Description
A disabled sortable is still able to receive elements from connected sortables and draggables (testcase only has draggable as source, was unable to include draggable test with latest because of bug #3979, but I tested it with 1.6rc4, same behaviour).
Tested with latest.
Attaching testcase.
Attachments (1)
Change History (4)
Changed January 29, 2009 01:04PM UTC by comment:1
Changed January 31, 2009 04:56AM UTC by comment:2
| component: | ui.sortable → ui.draggable |
|---|---|
| milestone: | TBD → 1.6 |
| version: | → 1.6rc5 |
This is actually a draggable bug as the functionality lives in draggable's connectToSortable code.
This problem does not exist for connected sortables, only draggables connected to sortables.
Changed February 01, 2009 04:37AM UTC by comment:3
| resolution: | → fixed |
|---|---|
| status: | new → closed |
Fixed in r1946.
Changed February 12, 2009 12:00PM UTC by comment:4
Still seeing this bug.
I meant: was unable to include *sortable* test (as source).