Skip to main content

Search and Top Navigation

#6082 closed bug (duplicate)

Opened September 20, 2010 04:49PM UTC

Closed September 20, 2010 05:07PM UTC

Last modified October 11, 2012 09:15PM UTC

Parent droppable takes precedence over dynamically created child droppable

Reported by: sslotsky Owned by:
Priority: minor Milestone:
Component: ui.droppable Version: 1.8.4
Keywords: Cc:
Blocked by: Blocking:

If a container div (known as container) is droppable and I dynamically create another div (known as emptyBox) and make emptyBox droppable, the drop event never fires for emptyBox, because the drop event for container is taking precedence. This container shows up in the list of droppables before any dynamically created droppable. As a result, the container is returned as the area in which to drop the draggable.

The droppable code should recognize that I'm trying to drop into emptyBox rather than container, but it does not, because container's drop event is taking precedence.

Attachments (0)
Change History (2)

Changed September 20, 2010 05:07PM UTC by scottgonzalez comment:1

resolution: → duplicate
status: newclosed

Duplicate of #6083.

Changed October 11, 2012 09:15PM UTC by scottgonzalez comment:2

milestone: TBD

Milestone TBD deleted