- From: Rick Byers <rbyers@chromium.org>
- Date: Tue, 16 Jun 2015 10:30:19 -0700
- To: "Patrick H. Lauke" <plauke@paciellogroup.com>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
- Message-ID: <CAFUtAY81rvdcxPNyekp2ORUfMgUStCQKvyoQiot-G7d9A2ys+A@mail.gmail.com>
On Tue, Jun 16, 2015 at 10:23 AM, Patrick H. Lauke <plauke@paciellogroup.com > wrote: > On 16/06/2015 17:42, Rick Byers wrote: > >> Button #0 is defined >> <http://www.w3.org/Submission/pointer-events/#button-states> as the 'pen >> contact' button, right? It seems we have at least the following two >> choices: >> >> 1) Allow firing pointerup / pointerdown for pen outside of contact >> scenarios. Eg. redefine button #2 to be just "barrel button" (instead >> of "pen contact with barrel button pressed). This seems like it's >> probably bad for web compatibility and might make it harder for >> developers to do common things. >> > > The "barrel button" is supposed to be equivalent to right-mouse/context > menu. As such, when pressed in the air, it should just fire pointermove (as > per spec) and click, rather than pointerup / pointerdown. > Same for any "left-mouse button" type buttons (Surface Pen lacks this - it > only has barrel, erase, and the non-remappable Microsoft OneNote one at the > top > https://www.microsoft.com/surface/en-gb/support/touch-mouse-and-search/surface-pen > - but Wacom Bamboo does have it - left-click, right-click, erase > http://us.wacom.com/~/media/WTC/Files/Manuals/Legacy/Bamboo%20Pen%20Bamboo%20Touch%20Bamboo%20Fun.pdf/ > (p 43)). Fire pointermove and click. > > 2) Allow the 'buttons' state to change while hovering. Apps that wanted >> to support "hover click" would need to watch pointermove for changes in >> buttons. This is a little more awkward, but it's a pretty special case >> anyway that I doubt most developers would ever want to support. So I'm >> OK with it being more difficult. >> > > For left-mouse button and right-mouse button / activation and barrel, and > possibly also for erase, would devs also be able to just listen for click > as usual? (not tested, but: does click in theory also have the same > button/buttons that you'd get from listening to pointermove instead?) Do we really want to fire 'click' without pointerup/pointerdown? Would that be web compatible? I was arguing that we wouldn't fire anything other than pointermove here... > > > P > -- > Patrick H. Lauke > -- > Senior Accessibility consultant > The Paciello Group (UK office) > http://www.paciellogroup.com > >
Received on Tuesday, 16 June 2015 17:31:11 UTC