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

Re: gotpointercapture/lostpointercapture on <button>s in IE

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Sun, 08 Jun 2014 01:40:08 +0100
Message-ID: <5393B0E8.2010504@splintered.co.uk>
To: public-pointer-events@w3.org
On 06/06/2014 09:38, Patrick H. Lauke wrote:
> On 06/06/2014 05:14, Rick Byers wrote:
>> Interesting.  It seems possible that websites could be broken by this
>> behavior in either case: they might not expect a gotpointercapture when
>> they don't think there's any code running that explicitly requests it,
>> or they may be surprised to see events that are behaving as captured
>> even though they never got a gotpointercapture event.
>
> Yes, after having had my fair share of automagic undocumented behavior
> (mostly from iOS/Safari) when it comes to touch events, I'd favour the
> path of least developer surprise, even if it just means adding a
> non-commital, fluffy, generic note at the end of the first bit of "10.
> Pointer Capture" (after Fig 4)  to the effect of:
>
> "NOTE: browsers MAY implement their own implicit pointer capture
> behaviour - for instance, for touch interactions, a browser may
> automatically capture the pointer as part of a tap on a native form
> control to allow for improved user interaction. As part of this
> behaviour, browsers MAY fire <code>gotpointercapture</code> and
> <code>lostpointercapture</code> events, even when no explicit pointer
> capture functions (<code>setPointerCapture</code> and
> <code>releasePointerCapture</code>) were called."

FWIW I filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=26013 with a 
slightly modified suggested note.

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 Sunday, 8 June 2014 00:40:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC