- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Sun, 23 Feb 2014 23:15:44 +0000
- To: public-pointer-events@w3.org
Turns out I was drawing the wrong conclusions from one of my tests (though this points to potential need for clarification elsewhere in the spec). I was basing my initial assumption on http://patrickhlauke.github.io/touch/tracker/mouse-tracker_touch-action-none.html - if you try using both a finger on a touchscreen and a mouse, you'll see how the circle that's drawn flip/flops between the two positions. The only events I'm binding to here are traditional mouse events, but the whole canvas has touch-action:none. However, as I wanted to make sure, I've now modified another little experiment of mine, http://patrickhlauke.github.io/touch/tracker/multi-touch-tracker-pointer.html - any pointer that has isPrimary set receives an additional circle outline ... and with this, I *do* see that both the first finger AND the mouse pointer are primary. So, disregard my initial misgivings about the language used in the note for 5.1.2. However, this raises the question if the spec should say anything about compatibility mouse events in the presence of more than one pointer that has the isPrimary flag set? It's probably implied currently that if there are two or more primary pointers, both will fire mouse events as well...but perhaps it's worth spelling out with a tiny note in section 11? "Note In the case where there are multiple <a href="...">primary pointers</a>, these pointer will all produce compatibility mouse events." ? P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Sunday, 23 February 2014 23:16:10 UTC