Re: [pointerevents] Clarify what event is `userEvent` to consider `click`/`auxclick` event target after `touchend` (or `pointerup`) (#508)

Well, I was trying to sort out the adjustment issue, but it seems complicated.

However, the root cause is, the spec does not assume that all browsers adjust touch event targets and/or mouse event targets are adjusted to different targets.

I think that aligning the target to `pointerdown` and `pointerup` is too risky for touch devices from usability/accessibility points of view. Especially when the `pointerdown` event is not consumed. I believe that if mouse events are not dispatched by consuming `poitnerdown`, `touchstart`, `touchmove` or `touchend`, etc, aligning the target must make sense since the web app is now aware of the target. On the other hand, if mouse events are fired, keeping the `click` related event targets as same as UI Events guarantees the backward compatibility especially web apps which handles only mouse events.

I'd like to suggest that the `click` event target alignment should be limited into less cases.

-- 
GitHub Notification of comment by masayuki-nakano
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2276970996 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 9 August 2024 01:10:11 UTC