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

Maybe there's something important I'm missing here about the process, but isn't that attitude causing a bit of a catch-22? If it's not added to the recommendation or specification, what incentive to the browsers have to implement it?

It seems to me the first step would be to just go ahead and add it, unless there's a solid reason why not. "Browsers are reluctant to adapt" doesn't seem surprising if it's not there in the specification they're trying to adhere to.

Or is there some other reason the browsers are against implementing this?

---
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-204867670