- From: François Billioud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Jun 2023 12:59:42 +0000
- To: public-css-archive@w3.org
> I think the scrollbar should not respond on elements with pointer-events: none, for 2 reasons: > > The scrollbar is part of the element While I agree that this is lexically correct, I don't see why this is a strong argument about what should be done here. Especially because: 1. If the scrollbar doesn't respond to clicks: - It is unexpected and frustrating for the end user to have a scrollbar they can't interact with - The dev has no way to make a component ignore mouse events but still be scrollable 2. If the scrollbar responds to clicks - The UI corresponds to what is actually possible for the user to interact with - If the dev really wanted the user to not be able to interact with the scrollbar, they could use `scrollbar-width: none;` In the end, IMO, the benefits for the community seems clearly in favor of the 2nd option. > Not every platform has space reserved for the scrollbar (macOS & mobile have overlay scrollbars) , meaning that being able to scroll the container would be dependent on the platform you're using. I don't see why this is related to the problem. The fact that the scrollbar is drawn aside or over the container doesn't change anything, does it? -- GitHub Notification of comment by Sharcoux Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9001#issuecomment-1611356224 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 June 2023 12:59:44 UTC