setDropEffect<T>(event: DragEvent, dropEffect: T): T
On Chrome 62, the dataTransfer.dropEffect property is reset to 'none' when the 'drop' event is
dispatched. As a workaround, we store it in a global variable.
The alternative workaround of recomputing it in the 'drop' event handler is problematic for a
different reason: the computation may depend on the modifier key states, and on Firefox 52, these
key states are not set in the 'drop' event.
On Chrome 62, the dataTransfer.dropEffect property is reset to 'none' when the 'drop' event is dispatched. As a workaround, we store it in a global variable.
The alternative workaround of recomputing it in the 'drop' event handler is problematic for a different reason: the computation may depend on the modifier key states, and on Firefox 52, these key states are not set in the 'drop' event.