- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Aug 2023 20:24:27 +0000
- To: public-css-archive@w3.org
> Can this work at the level of matching selectors by inventing functional forms for them like `:focus(visible, 30ms), :hover(3s)` or adding arguments to forgiving selectors like `:where(0 0 0, 300ms / :target, :active)`?
I'd be worried about that approach, because then you'd need a CSS way to actually trigger the popover/behavior. I.e. you'd need `:focus(visible,30ms) { trigger-popover-now: yes; }`. So far (and as far as I can see it going), that really belongs in the HTML part of this feature, right? Also, I think the feature I've described doesn't have an equivalent pseudo state already. `:focus` gets the keyboard part, `:hover` gets the mouse hover part, nothing gets the long-press part, and (most importantly) nothing enforces that you need to use them all together or someone will be broken.
--
GitHub Notification of comment by mfreed7
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9236#issuecomment-1692358052 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 August 2023 20:24:30 UTC