- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Aug 2024 15:20:30 +0000
- To: public-pointer-events@w3.org
Chromium does a similar [TouchAdjustment](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/page/touch_adjustment.cc;drc=2614c4fd91c5e9336c33dbcca82e9b8038e8ebff;l=556), and we find it independent from the `click` target change we are discussing here. Let me explain... Chromium's TouchAdjustment is done on "low-level" (`pointerdown` and `pointerup`) events only, and then `click` target is determined latter from the effective targets of those low-level events, w/o any further adjustments. The `userEvent` variable in the spec would affect only the `click` target in this case, and this target will be overridden only in the case the pointer has been captured. Without any pointer-capture by the JS, the adjustment would work as before; and with pointer-capture, the JS fully-determines target of the `click` (which I think correctly reflects the main motivation behind the `userEvent` wording in the spec). So TouchAdjustment complications feel like an isolated problem than `click` targets, at least until the planned change hits the Web. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2263340100 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 August 2024 15:20:31 UTC