Bug 17112

Summary: "Move" effect shows up like "disabled" when dragging
Product: WebKit Reporter: fengjin <fengjin>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: dbates, sebastian
Priority: P2    
Version: 523.x (Safari 3)   
Hardware: PC   
OS: Windows Vista   

Description fengjin 2008-01-31 01:47:07 PST 
Trying to drag a "<a>" element on a div element. In the div element's on dropping event, set the droEffect as "move". The actual effect is "disabled". However, setting to "copy" can succeed.

----- Here is the test html -----

<html>
<script language="javascript">

window.onload = function()
{
	var oDrag = document.getElementById("divDrag");	
	oDrag.addEventListener("dragstart", onDragDivStart, false);
	
	var oDrop = document.getElementById("divDrop");
	oDrop.addEventListener("drop", onDropDiv, false);
	oDrop.addEventListener("dragover", onDragOverDiv, false);
	oDrop.addEventListener("dragenter", onDragOverDiv, false);
}

function onDragDivStart(e)
{
	e.dataTransfer.setData("Text", "Mystery!!");
	e.dataTransfer.effectAllowed = "all";
	
	shwTxt("on drag div start!");
}

function onDropDiv(e)
{
	e = e || event;
	shwTxt("onDropDiv");
	var s = e.dataTransfer.getData("Text");
	shwTxt("onDrop : " + s);
}

function onDragOverDiv(e)
{
	e = e || window.event;
	var s = e.dataTransfer.getData("Text");
	e.dataTransfer.dropEffect = "move"; // "Copy" and "link" works
	shwTxt("ondragover : " + s);
	e.returnValue = false;
}

function shwTxt(s)
{	
	document.getElementById("divOutput").innerHTML += "<br>" + s;	
}
</script>

<body>

<div id="divDrop">drop on me</div>
<a href="www.google.com" id="divDrag">Drag me</a>

<div id="divOutput" style="top:200px"></div>
</body>
</html>
Comment 1 Sebastian Markbåge 2009-03-20 18:07:21 PDT 
I can confirm that this is the case on Windows. It seems to be Windows specific though because the Mac versions does allow move operations.
Comment 2 Daniel Bates 2009-10-15 20:54:28 PDT 
This issue has been resolved as of r49651 as part of the fix for bug #24731.