Sorry roc and jst but I won't be able to write a test for this. This is due to this line here under nsDomDataTransfer::GetFiles:
if (mEventType != NS_DRAGDROP_DROP && mEventType != NS_DRAGDROP_DRAGDROP)
return NS_OK;
The way we handle a dataTransfer in test drags is to capture it from a dragStart event, then use it in all other events. But, the dataTransfer saves its original event type (which is _START) and there is no way in JS to change this, so it triggers the early return.
I assume it's like this for a reason, eg. so a page can't read the files on a dragover event.
I did fix a couple bugs in finding this, but that's a whole day down the drain...
Created attachment 534375
Patch 2
Sorry roc and jst but I won't be able to write a test for this. This is due to this line here under nsDomDataTransf er::GetFiles:
if (mEventType != NS_DRAGDROP_DROP && mEventType != NS_DRAGDROP_ DRAGDROP)
return NS_OK;
The way we handle a dataTransfer in test drags is to capture it from a dragStart event, then use it in all other events. But, the dataTransfer saves its original event type (which is _START) and there is no way in JS to change this, so it triggers the early return.
I assume it's like this for a reason, eg. so a page can't read the files on a dragover event.
I did fix a couple bugs in finding this, but that's a whole day down the drain...