- From: GermanJablo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jan 2024 03:55:36 +0000
- To: public-css-archive@w3.org
Hi @devongovett, thanks for the detailed proposal. I agree that the behavior of `:hover` needs to be improved on touch devices, but I'm not sure excluding it from touch events is the right way. Mice and fingers are different interfaces and therefore there can be different interpretations about what some states such as hover mean on touch devices. One possible interpretation is that hover should not be possible with touch events as you propose, but I think another worthy of reflection is that hover could be activated while the finger is held down and on the target*. In other words, something could be considered "hovered" when it has what in react-aria you call [isPressed](https://react-spectrum.adobe.com/react-aria/usePress.html) state. *note: I know that react-aria's `onPress` event is "[reactivated](https://react-spectrum.adobe.com/blog/building-a-button-part-1.html)" if the mouse leaves the target and enters again, while this does not happen in the touch case. I suppose that this decision was made under the consideration that the user may want to scroll. A semi-related question then would be whether this `pressed/hovered` state should not be "reactivated" in touch events also if the user enters and exits the target and there is no scrollable container. I wouldn't be surprised if you've spent more time on these questions than anyone else, so you probably have good reasons to prefer the behavior you described. If so, I would like to know them :) -- GitHub Notification of comment by GermanJablo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7544#issuecomment-1897746234 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 January 2024 03:55:39 UTC