Re: [csswg-drafts] [css-pseudo-4] system colors for ::search-text (#10329)

The CSS Working Group just discussed `[css-pseudo-4] system colors for ::search-text`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> schenney: system colors for spelling, highlights, etc.<br>
&lt;fantasai> schenney: but we need colors for find-in-page<br>
&lt;fantasai> fantasai: How would that work on systems that don't have such colors?<br>
&lt;fantasai> dbaron: My memory is that the implementation needs to make something up<br>
&lt;fantasai> dbaron: preferably something reasonable in the context of the other colors<br>
&lt;fantasai> schenney: I think Chrome has ...<br>
&lt;fantasai> schenney: I think it would be ok to substitute browser-chosen colors<br>
&lt;fantasai> schenney: Assuming you have ::search-text pseudo-styling, and the browser chooses to support this, the author would be able to refer to the default system color<br>
&lt;fantasai> fantasai: couldn't they just say `revert`?<br>
&lt;fantasai> schenney: That would solve the problem<br>
&lt;fantasai> florian: if only about reverting the color, then `revert` works. But if want to use the same color because related ot search functionality, then you need to know what color that is<br>
&lt;emilio> Yeah, I thought the point of these is something like github implementing their own find-in-page looking like the browser<br>
&lt;florian> fantasai: I am hesitant to introduce this because, if it's use for revert, we should just use revert. However, if it is meant to be used in some other part of the UI to remind of the search color, we need a good story in UAs that don't use a color to signify the search<br>
&lt;florian> fantasai: until we've explored those use cases explicitly, I don't think we should add that.<br>
&lt;khush> q+<br>
&lt;fantasai> schenney: I suggest table this for now, and add to the discussion in the issue to bring up use cases for having the system color<br>
&lt;fantasai> schenney: so we have more information before trying to resolve<br>
&lt;annevk> fserb, yeah, you can organize a meeting through whatwg/html (I mentioned this last time we had the larger 2d canvas meeting as well); that's also a good place to make these proposals as they will impact the &lt;canvas> and 2D API<br>
&lt;astearns> ack khush<br>
&lt;fantasai> khush: Is there a platform that doesn't use highlight colors?<br>
&lt;fantasai> khush: what happens in that case?<br>
&lt;fantasai> schenney: A browser that doesn't use color highlighting, then it doesn't support ::search-text<br>
&lt;fantasai> khush: If a browser is not able to support it, would ignore the declaration<br>
&lt;fantasai> khush: would it make sense for such a browser to just say that it's not supported in @supports?<br>
&lt;emeyer> fantasai: I guess you could put the search color as an unsupported thing<br>
&lt;emeyer> fantasai: Will take this one back to the Safari team and see what they think<br>
</details>


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


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

Received on Wednesday, 12 June 2024 13:25:07 UTC