Closed jan-warchol closed 2 years ago
The code is susceptible to a race when we have several pointerLeave events processed one after another, without a gap to execute leaveContainer()
(which is scheduled with setTimeout). Then both leaveContainer()
callbacks were called one after another, the first one setting toEl = null
, and the second one running into this null.
Describe the bug I got an error like this:
To Reproduce Put several cards with no children next to each other. Drag another card rapidly over drop zones of the childless cards. It seems that dragging over cards with subtasks don't result in this error.
Organizer commit: 1f97005c