Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#8196 closed bug (worksforme)

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/

Change History (10)

comment:1 Changed 7 years ago by Scott González

Resolution: worksforme
Status: newclosed

Why would you set greedy to false on the inner?

comment:2 in reply to:  1 Changed 7 years ago by 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.

comment:3 Changed 7 years ago by 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.

comment:4 in reply to:  3 Changed 7 years ago by 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/

comment:5 Changed 7 years ago by Scott González

Use the accept option.

comment:6 in reply to:  5 Changed 7 years ago by 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.

comment:7 Changed 7 years ago by Scott González

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

comment:8 Changed 7 years ago by 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/

comment:9 Changed 7 years ago by Scott González

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

comment:10 Changed 7 years ago by nathanjosiah

That functionality is not documented at all.

Note: See TracTickets for help on using tickets.