- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Aug 2021 12:17:07 +0000
- To: public-pointer-events@w3.org
Just adding here, now that I thought it through some more: so the compat problems/issues would come about in user agents where PointerEvents have been implemented already using fractional coordinates, but the same implementation hasn't been extended to regular MouseEvents, right? If a browser decided to already implement fractional coordinates for MouseEvents, this would actually lead to problems again (essentially, the opposite type of problem this tries to address), right? In short, the problem only appeared because Chrome (and others?) didn't apply the CSSOM approach for MouseEvents, but *just* for PointerEvents, right? So my proposed sentence > For user agents that already implement this proposed extension, there are additional normative requirements when it comes to the <a><code>click</code>, <code>auxclick</code>, and <code>contextmenu</code> events</a> should probably more specifically be about > For user agents that already implement this proposed extension for PointerEvents, but <em>not</em> for MouseEvents, there are additional normative requirements when it comes to the <a><code>click</code>, <code>auxclick</code>, and <code>contextmenu</code> events</a> likewise, in > However, this change — when applied to <code>click</code>, <code>auxclick</code>, and <code>contextmenu</code> — has proven to lead to web compatibility issues with legacy code. it should probably read more along the lines of > However, this change — when applied to PointerEvents, but not to regular MouseEvents — has proven to lead to web compatibility issues with legacy code when applied to <code>click</code>, <code>auxclick</code>, and <code>contextmenu</code>. i.e. if the user agent hasn't implemented fractional coordinates anywhere (not in MouseEvents, not in PointerEvents), it's a non-issue. and it's also a non-issue if the user agent has applied this change to both MouseEvents and PointerEvents. it's only a problem when it's only implemented in one and not the other, right? -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/404#issuecomment-893412440 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 12:17:09 UTC