#8196 closed bug (worksforme)

Opened March 14, 2012 09:35PM UTC

Closed March 14, 2012 09:40PM UTC

Last modified March 15, 2012 04:11PM UTC

Nested droppable's drop event never get's fired.

Reported by: nathanjosiah Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.droppable Version: 1.8.18
Keywords: Cc:
Blocked by: Blocking:
Description

When one droppable is inside of another, only the outer droppable's events are fired.

Example: http://jsfiddle.net/Pz6G6/2/

Attachments (0)
Change History (10)

Changed March 14, 2012 09:40PM UTC by scottgonzalez comment:1

resolution: → worksforme
status: new → closed

Why would you set greedy to false on the inner?

Changed March 14, 2012 09:41PM UTC by nathanjosiah comment:2

Replying to [comment:1 scott.gonzalez]:

Why would you set greedy to false on the inner?

So that I am able to conditionally stop propagation to the outer element.

Changed March 14, 2012 09:44PM UTC by scottgonzalez comment:3

Feel free to start a discussion about the use cases that require this behavior. As far as I know, this is working as was designed many years ago.

Changed March 14, 2012 09:47PM UTC by nathanjosiah comment:4

Replying to [comment:3 scott.gonzalez]:

Feel free to start a discussion about the use cases that require this behavior. As far as I know, this is working as was designed many years ago.

Any idea why this shouldn't be allowed to work: http://jsfiddle.net/Pz6G6/4/

Changed March 14, 2012 11:43PM UTC by scottgonzalez comment:5

Use the accept option.

Changed March 14, 2012 11:47PM UTC by nathanjosiah comment:6

Replying to [comment:5 scott.gonzalez]:

Use the accept option.

I was referring to an arbitrary condition, the current time for example. Accept will not accomplish this. Please actually try to understand the problem before responding.

Changed March 15, 2012 12:20AM UTC by scottgonzalez comment:7

Please try to actually provide a use case before asking questions.

Changed March 15, 2012 03:32PM UTC by nathanjosiah comment:8

Touché, although in my last response I did. Anyway, I figured it out. In order for the events to propagate properly, you have to bind to the element manually, you can't use the "drop" property of the configuration object, I don't know if that would be considered a bug but it is definitely not expected behavior.

Example: http://jsfiddle.net/Pz6G6/7/

Changed March 15, 2012 03:42PM UTC by scottgonzalez comment:9

Callbacks are convenience methods for dealing with a specific instance. That results in intentional differences from binding to the associated events.

Changed March 15, 2012 04:11PM UTC by nathanjosiah comment:10

That functionality is not documented at all.