-
eric@webkit.org authored
Reviewed by Oliver Hunt. https://bugs.webkit.org/show_bug.cgi?id=25922 Fix dropEffect = "none" to work as expected. * fast/events/drag-to-navigate-expected.txt: Copied from LayoutTests/editing/selection/doubleclick-whitespace-img-crash-expected.txt. * fast/events/drag-to-navigate.html: Added. * fast/events/prevent-drag-to-navigate-expected.txt: Copied from LayoutTests/editing/selection/doubleclick-whitespace-img-crash-expected.txt. * fast/events/prevent-drag-to-navigate.html: Added. * fast/events/resources/file-for-drag-to-navigate.html: Added. * fast/events/resources/file-for-prevent-drag-to-navigate.html: Added. 2009-06-05 Eric Seidel <eric@webkit.org> Reviewed by Oliver Hunt. https://bugs.webkit.org/show_bug.cgi?id=25922 JS setting dropEffect = "none" causes tryDHTMLDrag to return DragOperationNone. Which is also the value tryDHTMLDrag previously used to indicate JS did not want to handle the drag. Make it possible for the DragController::try* methods to return a bool to indicate if javascript accepted or rejected the drag event, separate from the DragOperation. Tests: - fast/events/drag-to-navigate.html - fast/events/prevent-drag-to-navigate.html * page/DragController.cpp: (WebCore::DragController::dragEnteredOrUpdated): (WebCore::DragController::tryDocumentDrag): (WebCore::defaultOperationForDrag): (WebCore::DragController::tryDHTMLDrag): * page/DragController.h: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@45064 268f45cc-cd09-0410-ab3c-d52691b4dbfc
3c6ea8a1