Adam Lynch

My best workaround so far is applying the `isRateLimited` trait in this library to every method: ```raml #%RAML 1.0 Library uses: errors: errors.raml traits: isRateLimited: responses: >: headers: X-Rate-Limit-Limit: X-Rate-Limit-Limit...

Yeah. To be clear, my ideal thing would be that if no DOM mutations happened (well, in the containers at least) from start to end. So I'd expect the start...

OK so I've realised that the cloning feature could help achieve this if it was a little less limited. Right now, you can't have two containers with `lmdd-dispatcher`, but if...

>If cursor location is above or left the element top-left point, the dragged element will be placed before it. If I understand this correctly, I think it should be: ```diff...

Yeah, it's tough. Even if this was implemented, I assume doing scrollHeight, etc. checks up the DOM tree is too expensive so I guess the best thing would be to...

Apologies, they're all fine if `touch-action: none;` is added to the draggable items.

I guess I should leave it open so the demo will be fixed :)

Adding `touch-action: none;` breaks iOS Safari though (nothing happens at all when you drag). Note: I'm using http://codepen.io/adam-lynch/pen/PmPmeX to test (http://codepen.io/adam-lynch/full/PmPmeX to view just the result).

I did notice that if I turn on "paint flashing" in Chrome's dev tools, there are lot more (needless?) repaints with this library versus Dragula. - LMDD example: http://codepen.io/adam-lynch/pen/rmaYyZ. Video:...

Thanks for the info. >What you see while dragging is a clone of the original dom structure, and every element is positioned relatively and 'follows' the original element location and...