W3C home > Mailing lists > Public > www-svg@w3.org > August 2006

RE: SVG12: wheelDelta should be UIEvent.detail

From: Scott Hayman <shayman@rim.com>
Date: Tue, 8 Aug 2006 14:39:36 -0400
Message-ID: <1CA55DCF91707745A9B5091A303367E90648529F@XCH43YKF.rim.net>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: <www-svg@w3.org>

> From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] 

> * Scott Hayman wrote:
> >It seems odd to me, and here I am speaking on my own behalf and not 
> >that of the WG, that an event that inherits from MouseEvent could 
> >re-use the 'detail' attribute for something other than what it is 
> >specified for by MouseEvent.  I would think that this would be more 
> >confusing than introducing a new attribute.
> 
> In DOM Level 2 Events, only three mouse event types use 
> UIEvent.detail, click, mouseup, and mousedown. For all three 
> event types UIEvent.detail reflects the same information; in 
> order to avoid stating this for all three event types, the 
> specification just says once that if it is used, then like 
> this. The text there is not meant to establish a relationship 
> between the MouseEvent interface and UIEvent.detail.

Thanks very much for the clarification.

> >So the 'detail' attribute of MouseEvent in the DOM Level 3 
> Events spec 
> >no longer contains the information about the number of 
> button presses?
> >Isn't this a backwards compatibility issue?
> 
> There is no change, UIEvent.detail is still in use for click, 
> mouseup, and mousedown, and not in use for e.g. mousemove. If 
> some event object for a mousemove event in some 
> implementation specifies the number of mouse button presses 
> and releases, then that implementation operates outside of 
> what is specified in the DOM Events specification. I do not 
> think this is particularily confusing, it is not important for e.g.
> the mousemove event to inform about the number of clicks, but 
> it might be useful if it would carry information about, say, 
> the direction of the move, the current device velocity, or 
> what mouse gesture is being performed, a fixed relationship 
> between the MouseEvent interface and UIEvent.detail is 
> neither needed nor useful, so it's not there.

OK, I will bring this information back to the SVG WG to discuss the
possibility of using UI.detail for the wheel delta information.

Thanks again for your help in understanding this issue.

Cheers,
Scott



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Tuesday, 8 August 2006 18:39:57 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:35 GMT