[Bug 24706] Clarify when setPointerCapture is supposed to work

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24706

--- Comment #3 from Jacob Rossi [MSFT] <jrossi@microsoft.com> ---
"active pointers" != "active button state"

Hence, two separate entries in the glossary.

active pointer - pointers that can still produce further events.

pointer in the active button state - pointer with evt.buttons > 0.

So the *exception throws* (step 1) when you're trying to set capture to a
pointer that can't produce pointer events (e.g. a pointerId you made up or a
pointerId for a pointer that has gone away like a finger that left the screen).

The API *silently fails* (step 2) if you try to set it to a pointer that is
just hovering.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 18 February 2014 02:48:47 UTC