Re: [touch-events] createTouch has all the params as required, should probably have them optional (#58)

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

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/touch-events/issues/58#issuecomment-168826371