Hi, WebAPI fans-

I looked through all the issues and proposals, did some testing, and came up with what I hope will be a solid proposal for final wording on the issue of mousewheels. [1]

This is a solution that was discussed in a recent DOM3 Events telcon, and was favored by BitFlash and Microsoft, because it doesn't require as deep a hierarchy of interfaces as does the current model. [2] For the sake of argument, I put both models in the wiki [3], but I'm only asking for feedback on the first.

This interface is simpler for authors and for implementors, and I believe it covers the great majority of use cases. It is also, afaict, compatible with what's implemented today.

The one use case this doesn't seem to address is the canceling of wheel events along a single axis. I believe there is a suitable workaround, which I outline in the proposal.

My suggestion is that we specify this interface per my proposal, and if after implementation we find from author feedback that the more complex MouseOmniWheel/MouseMultiWheel interface is still needed, that can be implemented without causing conflicts (this would simply occupy the role that the existing MouseWheelEvent does).

[1] http://www.w3.org/2008/webapps/wiki/Mousewheel#Single_Event_With_Multiple_WheelDeltas [2] http://www.w3.org/TR/2007/WD-DOM-Level-3-Events-20071221/events.html#Events-eventgroupings-mousemultiwheelevents [3] http://www.w3.org/2008/webapps/wiki/Mousewheel#Multiple_WheelDelta_Events_With_Hierarchy

-Doug Schepers
W3C Team Contact, SVG, CDF, and WebAPI

Reply via email to