Seems as if this "startMouseCapture()" and "stopMouseCapture()" could be implemented by re-using DOM event's capture phase by adding event handlers to the capture phase of the #document and then "firing" those events directly on the target node.
In fact, I thought this was one of the primary use-cases for having the capture phase in DOM L2 events...? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Schepers Sent: Monday, September 22, 2008 10:20 AM To: public-webapps@w3.org; [EMAIL PROTECTED] Subject: Re: [D3E] Include mouse capture functionality Hi, Cameron- Cameron McCormack wrote (on 9/22/08 4:05 AM): > > I found the mouse capture methods[1] from the old SVG 1.2 Full WD to be > useful when writing web apps that did drag-and-drop. Since they’re not > really SVG-specific, I suggest adding them (similar functionality if > not exactly as in that document) to DOM 3 Events. These are implemented > in Batik. > > Thoughts? SVG 1.2 is evil and breaks the Web, and therefore we should avoid anything associated with it. That said, I think it's a good idea, and I'd be fine with adding it, or with putting it in a future events spec (along with multi-touch, pen/tablet input, etc.). Additionally, I've often wondered how the mouse sampling rate is determined, and it might be interesting to expose that rate through an API. In normal Web pages, this doesn't matter, but in Web applications (particularly though with a lot of dragging, drawing, or other mousemove-specific operations) it can help with performance. Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs
