I believe that only IE has the ondrag collection of event handlers built in. In any other browser, it is really a succession of mousedown and mousemove events.
jWeb New Media Design
Sent: Wednesday, March 15, 2006 6:16 PM
Excellent; that makes perfect sense. I assumed that the drag and drop
utility's 'events' were being sent to the browser in the same way as
generic events, something that probably isn't possible now that I
think about it. Thanks!
> What it comes down to is that the API methods in Drag and Drop (like
> onDragDrop) are not actual browser events (in the sense that a
> "click" is a browser event). onDragDrop is a method that fires
> during a particular "interesting moment" in a drag-and-drop
> interaction; you write code for that method to process that
> interesting moment, but it's not an event in the browser's sense of
> the term.
> In the background, some API methods are fired in tandem with browser
> events. A combination of a mousedown browser event and a mousemove
> browser event, taken together, instigate the Drag and Drop Utility to
> fire its startDrag method. That said, startDrag is just a method
> being fired -- not a browser event.
> Event Utility's addListener method is only used for adding event
> handlers for true browser events.