Open Bug 460801 Opened 15 years ago Updated 1 year ago
New D&D API: dragend is not dispatched if the source node was moved or removed during the drag session
I asked Neil, and he told that the "dragend" event is supposed to be dispatched on the document node if the source node was remove during the drag session. As I tested it, I figured out the following: 1. That's not implemented. 2. The event isn't dispatched on the sourcenode even if it was just moved on-drop or on-darg-over (and even if you called insertBefore without calling removeChild first). This sort of breaks all of my use cases for this event.
The spec is vague here as to what should happen. I just guessed that the best thing to do here is to just fire the dragend at the document if the node is no longer present or has been moved.
Neil - do you have a recommendation on blocking status here? How important is it that we go with your recommendation in comment #1 for 1.9.1?
It would be important if Asaf still needs the functionality, otherwise it isn't as the spec doesn't define the behaviour.
OS: Mac OS X → All
Hardware: PC → All
Asaf - do you need this for anything in particular?
At this point I don't think we'd take this on branch even with a patch, for API-compat reasons.
I'm seeing dragend events when I reorder tabs in the tabstrip (set a breakpoint in <handler event="dragend"> within tabbrowser.xml). However, this breakpoint isn't hit when I detach a tab to its own window. Can we mark this bug as resolved-worksforme?
I don't think any resolution has been determined here.
You need to log in before you can comment on or make changes to this bug.