- From: Stephen Chenney <notifications@github.com>
- Date: Tue, 12 Aug 2025 16:47:58 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 12 August 2025 23:48:02 UTC
schenney-chromium left a comment (w3ctag/design-reviews#1120) Thanks for the positive feedback on the use cases. Regarding Safari not implementing, two things come to mind: * The reason Safari will not implement is that they have a vendor-specific solution to the contrast problem implemented at the browser UI level. In particular, Safari find-in-page puts an overlay over the page to ensure contrast with the search UI. This overlay both addresses the use cases and prevents page-level control. * The missing feature will be detectable in Safari via @supports. I think the Safari UI would be an obvious flag to developers that custom search markers do not work, and that UI also prevents users from suffering significantly if a page fails to note the lack of compatibility. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1120#issuecomment-3181536098 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1120/3181536098@github.com>
Received on Tuesday, 12 August 2025 23:48:02 UTC