- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 13:14:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-pseudo-4] Add highlight pseudo for in-page search`. <details><summary>The full IRC log of that discussion</summary> <fantasai> schenney: Use cases for modifying the colors for find-in-page results on platforms that use colors<br> <fantasai> schenney: wouldn't apply in Safari's case<br> <fantasai> schenney: but both FF and Chromium browsers basically put a highlight the text<br> <fantasai> schenney: and some authors want to tweak colors to avoid conflicts or improve contrast<br> <fantasai> schenney: We prototyped, now want to ask if anyone has comments<br> <fantasai> emilio: we do implement this as a non-exposed system color so seems ok<br> <fantasai> emilio: they're hard-coded, so doesn't expose system colors<br> <fantasai> schenney: Page has no idea of what's actually highlighted<br> <fantasai> schenney: So don't think there are any new privacy issues here.<br> <astearns> fantasai: the main thing to worry about is if the author chooses intentionally-obscurre colors<br> <fserb> annevk, I see. Could we set up a "WHATWG subgroup to discuss canvas text"? Would that work?<br> <fantasai> schenney: There are people trying to prevent people from searching, e.g. suggestion to capture Ctrl+F<br> <fantasai> schenney: similar problem for selection and grammar-error<br> <fserb> annevk if we could have someone to participate at that from Apple, that would work.<br> <fantasai> schenney: If no other comments, then will go forward with previosu resolution.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3812#issuecomment-2162981247 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:14:19 UTC