Re: [w3c/touch-events] Why don't Touch objects have offsetX and offsetY properties like MouseEvent does? (#62)

I don't know anything about Pointer Events -- hopefully they end up having such useful things as `offsetX` and `offsetY`.

Why would a specification point out which browsers don't implement the specification properly? Isn't it up to the browser developers to read the specification and then follow it? Why would a specification exempt particular implementations from parts of itself!

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. Is that fair to say?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/touch-events/issues/62#issuecomment-204898078