This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As discussed on list http://lists.w3.org/Archives/Public/public-pointer-events/2014AprJun/0087.html I'd propose adding a note to "10. Pointer Capture" in the introductory section, after Fig 4: (slightly altered from my original suggestion) "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 (such as a button) to improve user interaction (allowing some finger movement to stray outside of the form control itself during the tap action). As part of this behaviour, browsers MAY fire <code>gotpointercapture</code> and <code>lostpointercapture</code> events, even though no explicit pointer capture functions (<code>setPointerCapture</code> and <code>releasePointerCapture</code>) were called."
Added as discussed: https://dvcs.w3.org/hg/pointerevents/rev/a6cecf9cf6bc The only change I made to the proposed text was to remove RFC2119 keywords since this is a note. Let me know if you see any issues with the text.
Two minor queries on this: - "Implicit Set of Pointer Capture" read slightly awkward. Could it be changed to "Implicit Pointer Capture" (as the text also deals with the implicit release of pointer capture, not just setting) - Should this be in an informative NOTE ?
Changing the title seems good. It already is in an informative note. I just put a heading above it to match the flow of implicit release of capture (and to get an entry in the ToC).
Ah, I think I understand what you mean better now. How does this change look? https://dvcs.w3.org/hg/pointerevents/rev/f260a1e7545b
Ah sorry, missed that it was already a note. Yup, all looks good to me now :)