Win32 modifier and mouse-button mask at drop time (MK_* flags), for a page that wants modifier-dependent behaviour. It does not change the drop effect reported to the drag source: copy for a drag from another application, the page's answer for one started in a page of this component.
Absolute filesystem paths, in DataTransfer.files order; empty when the drag carries no file list or the document origin is not trusted with paths.
Target of the .lnk shortcut at the same index of paths, or null; same length and same rules as the field of this name in dnd:enter.
The drag's session, as in dnd:enter.
Where the drag came from: self when it started in this window's page, other-window when it started in another window of the same foobar2000 (the main window or a popup), external for everything else, such as Explorer, another application, another foobar2000 process or a drag that started in a Default UI or Columns UI panel. The host reads it from a marker it adds to every drag that starts in a window it hosts; any program can imitate that marker, so treat the value as a hint about the drag's origin, not as a security check.
Cursor x in client-area physical pixels.
Cursor y in client-area physical pixels.
Payload of the
dnd:dropevent. The drag was dropped on the window. A drop lands only where the page accepts it, by callingpreventDefault()in its HTML5dragoverhandler, and elsewhere only when released within half a second of entering, before the page has answered.pathsis the final list, which the drag source may have changed sincednd:enter. The event can arrive before or after the page's own HTML5drophandler runs; calldnd.getPathsAsyncfrom that handler when the paths are needed together with the drop.