[w3c/uievents] Can't suppress the default action of non-primary button clicks (#107)

Long ago UI Events was changed to say that `click` [fires only for the primary mouse button](https://w3c.github.io/uievents/#event-type-click).  In trying to make blink conform to this, we've found there are some (rare) legitimate use cases where developers need to detect and possibly even cancel the default action associated with a middle button mouse click.

For example, in a tabbed UI clicking the middle button on a tab is expected to close it (not navigate to any link that happens to also be there).  Or in some scenarios (eg. GMail) an application can do a better job of opening a link in a new window itself via JavaScript rather than leaving the navigation up to the browser.

To address this need [@NavidZ has proposed](https://discourse.wicg.io/t/new-event-for-non-primary-button-click/1527) a new [`auxclick` event](https://navidz.github.io/auxclick/).  The basic premise is that ideally `click` is used just for the common action (since much usage of it won't ever think to check for things like unusual buttons) and a rarely used additional event is reserved for the special cases.

According to blink's "[incubation first standards policy](https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/PJ_E04kcFb8/ZXJXLJYYAAAJ)" we're [shipping this event](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/R8OehqGJzt0) based on [discussion in the WICG](https://discourse.wicg.io/t/new-event-for-non-primary-button-click/1527).  If all goes well (eg. we succeed in absorbing the web compat impact of no longer firing `click` for the middle mouse button, and other vendors become interested in implementing `auxclick` too) then we hope that the WPWG will consider adopting `auxclick`into UI Events.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/107