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

Solid reason to not add it would be to do that work in Pointer Events and leave TE as is for now - doing work in both specifications is double work for the implementors and editors, and it's not preferable. The extensions will most likely not get implemented (on Safari, as @patrickhlauke noted above) and will cause a fair bit of confusion.

It's complicated and messed up, but there is no good way around this without Apple changing their stance. That has not happened so far. Scattering the spec with "this is not implemented in Safari" is a workaround, but not a pretty one.

(Although I no longer have my affiliation outside of WPWG, hence have no say in this group I think this should probably be closed...)

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