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

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 with a 
slightly modified suggested note.

Patrick H. Lauke | |
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Sunday, 8 June 2014 00:40:22 UTC