Re: [touch-events] Add a constructor for TouchEvent and Touch (#16)

> Following the MouseEvent pattern would have the advantage of making it easier to port code from MouseEvent to TouchEvent (or vice-versa). Other than that, I have no strong feelings about this.

Right, and also between PointerEvent and TouchEvent too.

Personally I also think of the "client" co-ordinates as being the primary ones and the "page" ones being synthesized from that (at least that's how our implementation works).

I don't see much value in matching exactly the form of document.createTouch - [our data](https://www.chromestatus.com/metrics/feature/popularity#V8Document_CreateTouch_Method) suggests that that has extremely low usage in the wild.

That seems like enough reason to change to me.  I'll update the PR with that change soon.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/touch-events/pull/16#issuecomment-127699307