- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Jan 2016 22:08:57 +0000
- To: public-touchevents@w3.org
Both the test and the spec use 7 arguments, so I'm not seeing the issue there. But still they should perhaps be optional. They're certainly optional in blink, but I haven't tested other engines. @choniong WDYT? Also the "magic" clientX/Y behavior is how this API has always worked on at least Safari and Chrome AFAIK. There is some precedent for this sort of thing (eg. MouseEvent.pageX/pageY), but we ultimately decided not to follow that pattern for the constructors: #28 -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/touch-events/issues/58#issuecomment-168826371 using your GitHub account
Received on Monday, 4 January 2016 22:09:00 UTC