- From: Jon Jensen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 01:50:43 +0000
- To: public-css-archive@w3.org
One other interesting wrinkle is that all major browsers set both `clientX/Y` and `screenX/Y` to `(0, 0)` for synthetic pointer events. This potentially complicates option 3, since for consistency those properties should probably also be simulated. But that adds complexity, increases the risk of breaking websites, and starts to get at odds with [uievents](https://w3c.github.io/uievents/#mouseevent); while it doesn't speak to synthetic pointer events specifically, it does say that `0` is the default value. An argument could be made that the event didn't occur at any particular coordinate, so the default is in play. So perhaps the safer approach is option 4, i.e. just document the exception and file a Chrome bug to fix its weird `pageX/Y` handling. -- GitHub Notification of comment by jenseng Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8531#issuecomment-1457364422 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 01:50:44 UTC