- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Oct 2023 13:00:31 +0000
- To: public-pointer-events@w3.org
While I agree that the precision of a `double` may not be required here, it doesn't hurt either, right? I am worried about the non-zero compat risk that some code in the wild could break because of some assumption around precision. More on that compat point: we picked `double` here from the [TouchEvent spec](https://w3c.github.io/touch-events/#touch-interface) (where it has been like this for years). What if there is a comparison between altitude angles of a TouchEvent and the corresponding PointerEvent that assumes an 8-digit precision (i.e. "finer" than `float`)? This may sound impossible but consider this closely related experience: we failed to even [add precision to `click` coordinates](https://github.com/w3c/pointerevents/issues/100#issuecomment-818870316) because the integer coordinates of a MouseEvent was being compared with the coordinates of a `click` in a popular mapping website! Without a clear benefit, we should avoid such a risk IMHO. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/485#issuecomment-1750641217 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 October 2023 13:00:33 UTC