W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2015

Re: Hover click with pointer events

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Tue, 16 Jun 2015 16:25:30 +0100
To: public-pointer-events@w3.org
Message-ID: <55803FEA.30508@splintered.co.uk>
On 15/06/2015 13:48, Patrick H. Lauke wrote:
> On 22/04/2015 15:47, Timothy Dresser wrote:
>> The pointer event spec currently has no way of expressing a button press
>> on a hovering pen
>> (https://w3c.github.io/pointerevents/#dfn-chorded-buttons). There is no
>> allowed value for |buttons| if a pen is hovering with a button pressed.
>>
>> This is supported by modern styli, for instance the Wacom Bamboo has a
>> "Hover Click" feature (described on page 43 of
>> http://us.wacom.com/~/media/WTC/Files/Manuals/Legacy/Bamboo%20Pen%20Bamboo%20Touch%20Bamboo%20Fun.pdf).
>>
>>
>> Is this a scenario we want to enable?
>
> I'd actually love to see this scenario enabled (being able to get button
> states on hovered stylus/pen).
>
>  From some basic testing I just did with a Surface 3 and Surface Pen, it
> seems that the "eraser" and "right-click" buttons are not passed on when
> hovering (though in the case of the latter, Windows itself does
> recognise that it's pressed, as it displays an additional visual circle
> indicator on the "dot" that normally appears when hovering close enough
> to the screen). It's only once the pen tip touches the screen that
> e.buttons changes accordingly. (IE11/Win8.1 - don't have any means of
> testing the pen on a Win10/Edge setup just yet).

Expanding on this further, I think there are two aspects here, based on 
the current state of the spec and implementation:

a) should button states (button/buttons) be exposed also for "hovering" 
pens, not just for "Pen contact..." cases? In principle, I'd love to see 
this - and currently, at least on Surface 3 + Surface Pen, this is not 
the case (getting a pen into "hover" range fires pointerover, moving it 
fires pointermove, moving the pen out of the detection range fires 
pointerout ... but, regardless of the state of the buttons on the pen, 
button/buttons is not changed)

b) should devs be able to detect the difference between a hovering pen 
and a pen that has contact (in general), so as to be able to then 
differentiate a hovering click vs a touching click (specifically)? This 
would likely require an additional property on the event... e.contact?

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 16 June 2015 15:25:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 June 2015 15:25:56 UTC