We use contentEditable heavily in our app, and noticed lately that the way drag-and-drop works in Firefox has changed, and now instead of moving the position of the dragged element in the DOM, a copy is created. Moreover, the copy is apparently created before the dragstart event is called, so it will lose any changes made to the element during dragging. For us this breaks the way we used to track where a moved image ended up after being dragged and dropped. Test case detailed here: http://jsbin.com/ohuzaj/3
Is this a bug? Is there another way to tell where the element ended up after being dropped? Thanks Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
