Bug 20222 - Pointer events explicitly disallow compatbility with hover menus used by many web sites
Summary: Pointer events explicitly disallow compatbility with hover menus used by many...
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: This bug has no owner yet - up for the taking
Depends on:
Reported: 2012-12-03 22:43 UTC by Rick Byers
Modified: 2013-02-07 02:54 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Rick Byers 2012-12-03 22:43:41 UTC
Many websites have menus that open on mouse hover, eg. see the 'more' menus at the top of http://techcrunch.com/.

Touch events enables limited touch compatibility with such menus by sending mousemove,mousedown,mouseup events on tap (see http://www.w3.org/TR/touch-events/#list-of-touchevent-types although it's not precisely specified).  In practice, most such menus are usable with touch in browsers that implement touch events.

Pointer events, on the other hand, explicitly prohibits such compatibility by saying: "For input devices that do not support hover, a user agent must also fire a pointerout event after firing the pointerup event."

It may be unacceptable for browsers which already support this scenario via touch events to no longer support the scenario once as part of implementing pointer events.  Should the wording perhaps be relaxed to give the UA some explicit freedom in delaying that pointerout event?  Eg. perhaps "a user agent must also fire a pointerout event at some time after the pointerup event and before any other event is fired for the pointer".
Comment 1 Jacob Rossi [MSFT] 2013-02-07 02:49:05 UTC
Closing this issue as LATER. As discussed in the 2/5 telecon and on the list, we'll consider this in Pointer Events V2.