Re: [pointerevents-tests] Add movementxy attribute test for pointerevents (#4571)

Test is [now served here](https://w3c-test.org/submissions/4571/pointerevents/interaction-with-other-specs/pointerevent_movementxy-manual.html).  I can't get it to complete on current Chrome dev channel -
 the mouse one completes, but clicking 'skip' or using touch I still get "1 remain".

I was initially confused about the iframe and requirement that movement is kept to <10 pixels per event.  This is because the events that land over the frame are lost, right?  This is a same-origin iframe so it should be easy to also have listeners inside the frame which just call into some common code in the top document so that you can test both the events delivered to the top document and those delivered inside the frame.

Big picture, what I was wondering was - is it better to rely on relatively precise positioning like this (move from red to black), and/or should our test just verify that the movement sum exactly equals the change in client (or maybe screen) co-ordinates the way [the pointerlock tests do](https://github.com/w3c/web-platform-tests/blob/master/pointerlock/movementX_Y_basic-manual.html)?

/cc @scheib who may have input.  From a quick glance I didn't see any movementX/Y tests there which look explicitly at the iframe case (but maybe it was only our originally flawed PointerEvents implementation that would even suggest that such a test was worthwhile).





View on GitHub: https://github.com/w3c/web-platform-tests/pull/4571#issuecomment-274094988

Received on Friday, 20 January 2017 15:11:56 UTC