Allow instances to handle more than one element about draggable HOT 3 CLOSED

Hi @swang! Can you talk a little about the motivation for this? Why would you want a single event listener instead of one for each draggable?

from draggable.

My use case would be multiple draggable elements sitting under the same container. E.g. Being able to move pieces on a chess board.

Generally speaking delegating events to the container (a parent element) should use less memory than assigning events to each individual element. I'm assuming it's also quicker to instantiate that one event rather than multiple events. I've tried this w/ click events, but may also have to test mousemove events to see if there is still the same improvement.

So if I have a page that has several different chessboards that show different scenarios. Instead of having to create an event for every piece of every board. I can just define one listen event delegator to handle it.

Doing this also allows me to add/remove draggable elements without having to redefine a new draggable instance each time an element is created since the event delegate handles it.

from draggable.

Generally speaking delegating events to the container (a parent element) should use less memory than assigning events to each individual element.

This is not really the case with modern browsers, and hasn't been for some time. If you run a benchmark, you'll see there is no difference between the delegated and non-delegated versions.

I'm assuming it's also quicker to instantiate that one event rather than multiple events

Maybe by, like, nanoseconds? Have you tried profiling this to get some real numbers?

This doesn't seem like a good use case to me. If you can produce a benchmark that shows an improvement with delegation, I'd be more than happy to support this.

from draggable.