[Webkit-unassigned] [Bug 30102] [Win] Drag cursor does not show not-allowed cursor on invalid drag-and-drop operation.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 5 18:35:14 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30102
Daniel Bates <dbates at webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #40674| |review?
Flag| |
--- Comment #2 from Daniel Bates <dbates at webkit.org> 2009-10-05 18:35:13 PDT ---
Created an attachment (id=40674)
--> (https://bugs.webkit.org/attachment.cgi?id=40674)
Patch with manual test case
I could not think of a good name for the function
draggingSourceOperationMaskToDragCursors in file WebDragClient.cpp. I am open
to suggestions.
We cannot test this using DRT because DRT looks at the programmatic drop cursor
and until bug #24731 is fixed this value is hard-coded to DragOperationCopy.
That is, there is a discrepancy in the Windows build between the Windows
API-based drop effect and the WebKit drop effect. Because DRT cannot read the
screen buffer to determine the cursor, a manual test is needed.
--
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