Bug 34970 - onDrop does not fire and -webkit-user-drop has no effect
Summary: onDrop does not fire and -webkit-user-drop has no effect
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL:
Keywords: GoogleBug, HTML5
Depends on:
Blocks:
 
Reported: 2010-02-16 02:09 PST by Pat
Modified: 2010-02-16 02:32 PST (History)
1 user (show)

See Also:

Attachments
Testcase (3.83 KB, text/html)
2010-02-16 02:09 PST, Pat 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pat 2010-02-16 02:09:48 PST 
Created attachment 48796 [details]
Testcase

See the attached page for a test case.  To reproduce: load page, then try to drag a word onto the target.

Expected result: An alert that says "drop" should appear.  Also, the cursor should show that dropping is permitted.

What happens: Nothing.  onDrop does not fire the event.  The cursor shows that dropping is not allowed.

All other events (ondragstart, ondrag, ondragend; ondragenter, ondragover, ondragleave) successfully fire, except for ondrop.

Reproduced on:
 WebKit nightly r54757
 Chrome 5.0.317.2

Safari 4.0.4 official OK.
Comment 1 Pat 2010-02-16 02:32:59 PST 
My apologies, this seems to only affect Google Chrome right now.

Latest Webkit works according to the HTML spec for drag & drop.

dropEffect must be set for the dragover handler because the default dropEffect is nothing ('do not drop').

evt.dataTransfer.dropEffect = 'move';