Re: [csswg-drafts] [css-pseudo] allowing ::search-text:current its own overlay (#10527)

The CSS Working Group just discussed `[css-pseudo] allowing ::search-text:current its own overlay`, and agreed to the following:

* `RESOLVED: Give ::search-text:current its own overlay`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> schenney: for context, there's a notion of highlight overlays that have a stacking order<br>
&lt;kbabbitt> ... overlay with defined order on overlays<br>
&lt;kbabbitt> ... pseudo for search text where you specify search text current which is currently active find in page instance<br>
&lt;kbabbitt> ... just search text is the inactive ones<br>
&lt;kbabbitt> ... this question is whether currently active one and active ones should have spearate highlight overlays<br>
&lt;kbabbitt> .. with current active on top of active in paint order<br>
&lt;kbabbitt> ... makes it easier to implement<br>
&lt;kbabbitt> ... change spec to say that search text current is one overlay, search text is another<br>
&lt;kbabbitt> ... define order as current over regular<br>
&lt;kbabbitt> florian: search-text includes current?<br>
&lt;kbabbitt> schenney: in principle they're mutually exclusive states<br>
&lt;kbabbitt> ... can't be both active and inactive<br>
&lt;kbabbitt> ... in practice ordering doesn't come up<br>
&lt;kbabbitt> florian: not one is superset of other, they're mutually exclusive?<br>
&lt;kbabbitt> schenney: yes<br>
&lt;kbabbitt> astearns: questions or concerns?<br>
&lt;kbabbitt> Proposed: Give search-text-current its own overlay<br>
&lt;kbabbitt> RESOLVED: Give ::search-text:current its own overlay<br>
&lt;kbabbitt> fantasai: if it's its own overlay, are we in same situation as :hover?<br>
&lt;kbabbitt> ... where we have multiple things and we're selecting one?<br>
&lt;kbabbitt> schenney: no<br>
&lt;kbabbitt> ... if you type multiple words into find in page, all words will match search-text-current<br>
&lt;kbabbitt> ... and get current highlighting<br>
&lt;kbabbitt> ....everything else will get search-text<br>
&lt;kbabbitt> florian: the interaction between this and hover<br>
&lt;kbabbitt> ... would we want it to be possible to do some effect when hovering search texty<br>
&lt;kbabbitt> ... vs hovering current search text<br>
&lt;kbabbitt> ... then it would need to be a subset<br>
&lt;kbabbitt> ... not sure it's a real use case but if it is we need to work it out<br>
&lt;kbabbitt> schenney: would work it out as part of hover<br>
&lt;kbabbitt> florian: we can only work it out as part of hover if ...<br>
&lt;kbabbitt> .... you just said they're mutually exclusive rather than a subset<br>
&lt;kbabbitt> ...<br>
&lt;kbabbitt> ... that seems to be incompatible with wanting to be able to highlight all search text when you hover current one<br>
&lt;kbabbitt> schenney: yes<br>
&lt;kbabbitt> florian: current one would also need to be part of everything else<br>
&lt;kbabbitt> ... so when you highlight one chunk, change the style of everything<br>
&lt;kbabbitt> ... not sure it's a real thing people want to do but defining them as mut ex makes it impossible to do<br>
&lt;kbabbitt> schenney: we've already defined them as mut ex so we'd ahve to revisit<br>
&lt;kbabbitt> ... but I see what you're saying<br>
&lt;kbabbitt> ... will open another issue for this<br>
&lt;kbabbitt> ... plan to open a bunch of issues related to hover<br>
&lt;kbabbitt> ... I'll make sure that gets addressed as part of hover stuff<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10527#issuecomment-2622992202 using your GitHub account


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

Received on Wednesday, 29 January 2025 22:18:54 UTC