Test for releasing pointers when pending_capture != actual_capture |
|||
Issue descriptionWith lazy capture updates through pendingPointerCapture, releasePointerCapture can have two interpretations when pending capture is different from actual capture. We need a test to cover such cases. But most importantly, is the spec precise enough? I think we should shift "pending + actual capture" targets upon releasing, to be precise. Is it right? Here are the cases I have in my mind: capture@A, capture@B, release@A (no PEs in between) capture@A, capture@B, release@B (no PEs in between)
,
Aug 30 2016
Spec has no ambiguity now I believe, after Navid's PR: https://github.com/w3c/pointerevents/pull/137 We still want to add a test. Let me clarify the cases I meant above, looks like the "no PEs" above are confusing: capture@A, pointermove, capture@B, (no PEs in between) release@A capture@A, pointermove, capture@B, (no PEs in between) release@B
,
Aug 30 2016
I'd like to work on a wpt test directly for this one. Is it okay to add something like this: capture@A, pointermove, capture@B, (no PEs in between) release@A (nothing should happen) release@B (capture should be released?)
,
Aug 30 2016
Yes, this covers both cases.
,
Sep 8 2016
I updated one of the existing tests to cover this case here: https://github.com/w3c/web-platform-tests/pull/3665 ptal whenever you get a chance.
,
Sep 8 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dtapu...@chromium.org
, May 24 2016Status: Assigned (was: Unconfirmed)