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

[nathanjosiah]

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

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

[Scott González]

Why would you set greedy to false on the inner?

[nathanjosiah]

Replying to 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.

[Scott González]

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.

[nathanjosiah]

Replying to 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/

[Scott González]

Use the accept option.

[nathanjosiah]

Replying to 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.

[Scott González]

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

[nathanjosiah]

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/

[Scott González]

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

[nathanjosiah]

That functionality is not documented at all.