- From: Philipp Rudloff via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 Nov 2024 10:10:52 +0000
- To: public-css-archive@w3.org
@tabatkins Apologies, I somehow managed to completely invert the requirements I had in mind while writing them down. I updated [my post](https://github.com/w3c/csswg-drafts/issues/6280#issuecomment-2490963833) and also expanded the explanation somewhat. My intention was to achieve the inverse effect: to allow a scroll on a card to "chain up" (or "through") the card and fire on the element behind it. `pointer-events: none` does this, but it also, of course, makes the cards non-interactive for pointer interactions (e.g. let's say for simplicity's sake the card would only have links). Most likely this one of these cases where in isolation, such an API could make sense, but overall, it's probably too big of a UX infraction if not handled extremely carefully should the card itself need to have any scrolling content. -- GitHub Notification of comment by kleinfreund Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6280#issuecomment-2495426633 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 23 November 2024 10:10:53 UTC