- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 11 Jun 2025 16:35:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Selecting ::scroll-marker based on relationship to scroll target`, and agreed to the following: * `RESOLVED: add :target-before and :target-after` <details><summary>The full IRC log of that discussion</summary> <JoshT> astearns: are we any closer or go back to the issue?<br> <JoshT> flackr: there is one issue: target past and future to refer to the target current marker<br> <JoshT> ... it wouldn't solve the other problem of styling the thing targetted. I don't know if we have a proposal for that yet<br> <JoshT> TabAtkins: I don't like the name past and future. would prefer before and after<br> <JoshT> ... but we are saying yeah to it and no one commenting on it otherwise<br> <JoshT> ... do we want to resolve to do it?<br> <JoshT> fantasai: I can see why that makes sense. but we do have 'current' which pairs with past and future<br> <JoshT> TabAtkins: I think current works on various axis<br> <JoshT> ... I think before, current and after are reasonable adjectives<br> <JoshT> florian: it doesn't feel like a different axis.<br> <JoshT> TabAtkins: there is no time in 'steps'.<br> <JoshT> fantasai: should we go back and look at other places where we use these terms?<br> <JoshT> TabAtkins: the pseudo-class for ????? uses it as well.<br> <fantasai> s/?????/highlights API<br> <schenney> Specifically ::search-text:current<br> <JoshT> astearns: no strong opinion either way. would like to use before and after consistently<br> <JoshT> fantasai: currently used for time axis, so maybe we should revisit it<br> <schenney> Nobody has implemented past/future in this context, so no problem changing it.<br> <JoshT> TabAtkins: should be brought up in separate issue<br> <fantasai> s/revisit it/revisit usage in the highlights api/<br> <JoshT> astearns: resolution to add target-before and target-after?<br> <JoshT> TabAtkins: match the other targets in the scroll marker group before or after the currently targeted one<br> <JoshT> florian: are we talking about a pseudo-class before and after?<br> <JoshT> TabAtkins: yes<br> <JoshT> florian: I think this is confusing having :before and :after<br> <kizu> `:target-before:target::before`<br> <JoshT> TabAtkins: it's :target-before and :target-after<br> <JoshT> astearns: would anyone like more time to consider this?<br> <JoshT> ... anyone who would object?<br> <JoshT> ... names can be bikeshedded<br> <JoshT> fantasai: I'm OK but Tab can you open issue about highlight API?<br> <JoshT> TabAtkins: yes<br> <JoshT> RESOLVED: add :target-before and :target-after<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11600#issuecomment-2963486023 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 June 2025 16:35:15 UTC