[csswg-drafts] [selectors-4][css-pseudo-4] meaning of ::search-text:current(…), :past, :future (#10298)

delan has just created a new issue for https://github.com/w3c/csswg-drafts:

== [selectors-4][css-pseudo-4] meaning of ::search-text:current(…), :past, :future ==
We resolved that ::search-text (#3812) should have a :current (#10212) state for the active search result, but :current also has a [functional form](https://drafts.csswg.org/selectors/#selectordef-current), where `:current(x, y)` matches any current element (or innermost ancestor) that also matches `x, y`.

0. **Is the list of compound selectors in [:current(…)](https://drafts.csswg.org/selectors/#selectordef-current) a <forgiving-selector-list>?** On the one hand, selector lists are normally invalid when they contain an invalid selector, but on the other hand, “like ‘:is()’” suggests it should be forgiving. If so, we should also update [this note](https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list).

1. **What does `::search-text:current(x, y)` mean?** Does it mean the innermost `x` or `y` that contains the active search result (which we probably want to forbid, since it would allow highlights to affect layout), or the ::search-text of that innermost `x` or `y` (which may have tricky :has()-like perf implications), or something else? We propose that `::search-text:current(…)` be invalid, for now.

2. **What do [:past](https://drafts.csswg.org/selectors/#the-past-pseudo) and [:future](https://drafts.csswg.org/selectors/#the-future-pseudo) mean on ::search-text?** We propose that these also be invalid, for now, since no known UA distinguishes between search results on either “side” of :current.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10298 using your GitHub account


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

Received on Thursday, 9 May 2024 08:39:39 UTC