- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Aug 2021 17:42:27 +0000
- To: public-pointer-events@w3.org
> Just pushed a change to this PR to clarify this further. I _think_ this now more accurately explains where the problem lies, and when this requirement needs to be implemented. I am afraid it was more accurate before this last commit! Let me add a few points to focus on, in case they call for more discussion: - `Double` coordinates (as per CSSOM View spec) are known to be better but we can't move MouseEvent coordinates away from `long` for compat reasons. We logically _expect_ that all UAs would pick `double` coordinates for PointerEvents (as per CSSOM) even if those UAs remain stuck with long coordinates in MouseEvents (as per UI Event spec). - The _expectation_ above applied only to "original" PointerEvents (`pointerdown`, `pointermove` etc). The "newly promoted" PointerEvents (`click`, `auxclick` and `contextmenu`) suffer from the similar compat issues like MouseEvents. - The two points above are orthogonal to compat MouseEvents. - The compat event section only defines the firing of followup MouseEvents, without touching any other details of the events---because those details belong to the UIEvent spec. Adding more details here means more redundancy and may possibly call for more monkey-patching. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/404#issuecomment-893657749 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 August 2021 17:42:28 UTC