Re: Hover click with pointer events

On Thu, Jun 18, 2015 at 8:17 AM, Tim Dresser <tdresser@google.com> wrote:

> I suspect we'll want the spec to phrase this as optional, as there's
> likely hardware which won't support this feature.
>
> What's the advantage of adding a pointerbuttonchange event instead of
> dispatching pointermove events? Would this just be an improvement in
> developer ergonomics?
>

This was my question as well.  And if we have pointerbuttonchange, then why
not also pointerpressurechange, pointergeometrychange, etc.   We recently
argued that we thought Apple's force click scenarios could reasonably be
built directly on pointer events without need for forcechange events - this
seems similar to me.

Not that I'm opposed to new events per se, but it does add some complexity
for a pretty niche scenario here.  I can't help but wonder if it's worth
it...

Rick

On Wed, Jun 17, 2015 at 6:56 PM Patrick H. Lauke <redux@splintered.co.uk>
> wrote:
>
>> On 17/06/2015 23:19, Jacob Rossi wrote:
>> > On Tue, Jun 16, 2015 at 10:26 AM, Tim Dresser <tdresser@google.com>
>> wrote:
>>
>> >>   I'd be fine with forcing developers to listen for
>> pointerup/pointerdown events to keep track of hover.
>> >
>> > Yeah I agree. This seems like the safest place to start.  I opened up
>> an issue to track this and will take a look at a spec patch to address this.
>>
>> Just to confirm my suspicion that a hovered stylus does, predictably,
>> have a pressure of 0...so getting a pointermove event with zero pressure
>> it's a fair bet that it's a hovered (at very very gently brushing
>> against the screen) movement, for instance. As such we're probably right
>> not to magic up a new touching/not touching attribute.
>>
>> 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
>>
>