- From: Sangwhan <sysbot+gh@w3.org>
- Date: Sun, 03 Apr 2016 07:32:13 +0000
- To: public-touchevents@w3.org
> Anyway, I suppose the question I'm asking in this ticket (why do these properties exist in MouseEvent but not Touch) is sort of answered. It appears the answer is that the spec is more a reflection of what the browsers already have, rather than a specification written with good standards and practices in mind which browsers are supposed to adhere to, and browsers just didn't add these properties to the Touch object. Yes. Touch Events in particular is not a very well designed event model in many ways. The spec is a documentation of existing behavior. There are multiple technically sane solutions to fix all of these issues and more, it's just that there are political complications which obstruct the WG/CG from doing so. -- GitHub Notification of comment by cynthia Please view or discuss this issue at https://github.com/w3c/touch-events/issues/62#issuecomment-204898204 using your GitHub account
Received on Sunday, 3 April 2016 07:32:16 UTC