Skip to main content

Bug Tracker

Side navigation

#10727 closed bug (invalid)

Opened November 08, 2011 10:56PM UTC

Closed November 08, 2011 11:01PM UTC

Last modified November 09, 2011 04:54PM UTC

With 1.7 droppable() event target changed

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.7
Keywords: Cc:
Blocked by: Blocking:

Under 1.6.2 the event target on a droppable drop was the element that the drop occurred to, whereas with 1.7 the event target becomes the element being dropped.

If you drop 'one' onto 'two', under 1.7 the console shows 'one' whereas under 1.6.2 it shows 'two':




<!-- <script src="" type="text/javascript"></script> -->

<script src="" type="text/javascript"></script>

<script src="" type="text/javascript"></script>


function OnDrop(e, ui)




$(document).ready(function ()



$("#two").droppable({ drop: OnDrop });





<div id="one">one</div>

<div id="two">two</div>



Attachments (0)
Change History (3)

Changed November 08, 2011 11:01PM UTC by dmethvin comment:1

resolution: → invalid
status: newclosed

This should be reported to the UI folks at and they can determine if it is caused by a core bug. Thanks!

Changed November 08, 2011 11:06PM UTC by anonymous comment:2

Sadly every significant operation I try on that site crashes.

Changed November 09, 2011 04:54PM UTC by comment:3

Here is the UI ticket:

I do find it somewhat disturbing that while they may 'fix' it, fundamentally an underlying assumption of some kind has changed, and it's not clear to me if that's intentional or not. In other words, how many more things would be expected to break due to this change?