- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Sat, 28 Sep 2024 01:04:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Bikeshed pseudoclasses for active scroll-marker`, and agreed to the following: * ``RESOLVED: `:current` is better than `:checked`, issue remains open while we look for better alternatives`` <details><summary>The full IRC log of that discussion</summary> <emilio> flackr: so in scroll-markers spec I used :checked, because it's a state that doesn't involve focus... but :checked is associated with form elements<br> <kizu> +1 to `:current`<br> <emilio> ... there was a suggestion to use `:current`<br> <emilio> ... related to `:past` and `:future`, tab objected to that<br> <fantasai> -> https://github.com/flackr/carousel/issues/28#issue-2406219421<br> <emilio> ... we can't use :active because things become :active while you interact with this<br> <miriam> q+<br> <kizu> `:scroll-target`?<br> <emilio> fantasai: fun historical link, on IE clicking a link to the same page would remain `:active`<br> <emilio> flackr: so there's precedent for `:active`!<br> <fantasai> s/to the same page/to a target on the same page/<br> <kizu> `:active-anchor`<br> <Rossen9> ack miriam<br> <fantasai> s/`:active`/`:active` as long as the browser was still targetting that ID/<br> <emilio> miriam: seems tab's objection to `:current` seems more about `:past` and `:future`<br> <emilio> ... `current` matches what I'd use in JS which is aria-current<br> <emilio> flackr: wouldn't mind `:current`<br> <keithamus> +1 to :current<br> <emilio> fantasai: my only concern with current is possible conflict with a different meaning of `:current`<br> <ydaniv> +1 to miriam<br> <emilio> emilio: does any browser implement `:current` with any other meaning?<br> <Zakim> astearns, you asked to be reminded at this time to go home<br> <emilio> (nobody knows)<br> <emilio> emilio: Gecko doesn't at least<br> <emilio> q?<br> <emilio> flackr: another thing to think about is whether `:current` makes sense for all use cases<br> <emilio> ... can't think of any, even if you use it for tabs, or scrolling content, or ???, `:current` feels right<br> <flackr> s/???/slides<br> <emilio> fantasai: current was designed to work as a styling for navigation or so for screen readers<br> <emilio> ... currently used for captions<br> <emilio> ... like the fact that it means the right thing<br> <emilio> ... but if we did this and we ever wanted to do something like that then it'd conflict<br> <emilio> flackr: should we try to resolve on `:current` for now?<br> <emilio> fantasai: yeah I think `:current` is better than `:checked`, we can keep the issue open<br> <emilio> astearns: reading MDN of the current use of `:current` it'd match the ancestor of the thing that's currently played<br> <emilio> ... so if you style a marker with `:current` it'd pop out everywhere<br> <emilio> dbaron: is it video or vtt?<br> <emilio> astearns: vtt<br> <emilio> emilio: isn't the vtt tree scoped?<br> <emilio> fantasai: if it isn't it should<br> <emilio> Rossen9: what's the issue with `:active`?<br> <emilio> fantasai: while you're clicking on the button that's `:active`<br> <emilio> ... don't mind reusing it but if you need that meaning...<br> <emilio> flackr: that wouldn't work for the link version of scroll markers<br> <emilio> fantasai: yeah you probably want something different then<br> <astearns> s/style a marker/style a marker for a carousel tab that is currently playing a video/<br> <emilio> [jokes]<br> <emilio> emilio: seems people thought `:current` is better than `:checked`<br> <fantasai> https://www.w3.org/TR/selectors-4/#time-pseudos<br> <emilio> PROPOSED: `:current` > `:checked`, issue remains open while we look for better alternatives<br> <emilio> RESOLVED: `:current` is better than `:checked`, issue remains open while we look for better alternatives<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10918#issuecomment-2380329944 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 September 2024 01:04:07 UTC