- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 22 Jan 2014 10:51:44 +0000
- To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
I know "click" and "contextmenu" aren't considered compatibility mouse events (and rightly so), but I'm wondering if the spec should still mention something more explicit about them in relation to pointerup. As an initial suggestion, based on my proposed patch for the list of event types table, maybe adding something to the default action entry for pointerup "Varies: when the pointer is primary, all default actions of mouseup" change to "Varies: when the pointer is primary, all default actions of mouseup; dispatch click or contextmenu events [...]" though on the other hand, I can see how this may require too much extra explanation (as it depends on the mouse button pressed, for instance), and I guess it would also (at least for contextmenu) need a similar note about long-pressing (on pointerdown?) for touch interfaces? Good idea or not? Now that I've written it out, it actually looks a lot hairier than I first anticipated. Maybe a new note after the table instead? Something a bit generic mentioning that user agents may then also dispatch click/contextmenu depending on ... something? P -- Patrick H. Lauke ______________________________________________________________ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com | http://flickr.com/photos/redux/ ______________________________________________________________ twitter: @patrick_h_lauke | skype: patrick_h_lauke ______________________________________________________________
Received on Wednesday, 22 January 2014 10:52:04 UTC