[Webkit-unassigned] [Bug 57185] New: ondrop event isn't fired for contentEditable while respecting normal behavior
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Mar 27 09:39:25 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=57185
Summary: ondrop event isn't fired for contentEditable while
respecting normal behavior
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: HTML Editing
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: amla70 at gmail.com
Created an attachment (id=87076)
--> (https://bugs.webkit.org/attachment.cgi?id=87076&action=review)
Sample testcase
The only way to catch the onDrop event for contentEditable elements is to listen for ondragover and cancel that event, but in that case the normal behavior of allowing drag&drop is broken.
In https://bugs.webkit.org/show_bug.cgi?id=3582#c5 it's stated that this is the expected behavior by the spec, but that's hardly useful for real usage. Firefox and IE both fire the onDrop event when something is really dropped into the content.
An example of why we want to listen for that event: http://dev.ckeditor.com/ticket/7422 in order to provide Undo/Redo management we must track the changes to the document. Due to this bug, in Webkit we can opt to not cancel the onDragOver event and so the onDrop isn't fired, or cancel it and then the user can't drag anything.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list