Re: [csswg-drafts] [css-overflow-5] Bikeshed pseudoclasses for active scroll-marker (#10918)

The CSS Working Group just discussed `[css-overflow-5] Bikeshed pseudoclasses for active scroll-marker`, and agreed to the following:

* `RESOLVED: Use :target-current for the name.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> flackr: :checked is confusing (to use for the active scrol lmarker in a group)<br>
&lt;TabAtkins> flackr: we resolved :current is better, but it also has conflation with the other meaning of :current, and possibly used in same context<br>
&lt;TabAtkins> flackr: so I've proposed we go with :target-current<br>
&lt;TabAtkins> flackr: this combines the fact that you're referring to the "target" of the marker, similar to :target pseudo we already have, and that the target is "current" in the ways we thought made sense before.<br>
&lt;TabAtkins> flackr: but as a different pseudo this is separately targetable from :current<br>
&lt;TabAtkins> (+1 to the name)<br>
&lt;fantasai> +1 to new pseudo-class, :target-* seems like a good idea, and :target-current seems fine<br>
&lt;TabAtkins> astearns: you quoted that this has the potential to set precedent for upcoming specs, do you know what was meant there?<br>
&lt;TabAtkins> flackr: i don't know if there was a ref to a specific other decision<br>
&lt;TabAtkins> astearns: anyone who thinks :target-current is not the right choice and would like something else?<br>
&lt;fantasai> I'm also ok with :target-shown<br>
&lt;TabAtkins> flackr: suggestions with "shown" or visbility have come up, i'm shying away from those because several potential targets might be currently visible. "current" has a stronger notion of us determining that one is active.<br>
&lt;TabAtkins> astearns: proposed to use :target-current<br>
&lt;TabAtkins> RESOLVED: Use :target-current for the name.<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-2489057359 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 November 2024 16:32:48 UTC