Re: [w3ctag/design-reviews] CSS find-in-page highlight pseudos (Issue #1120)

schenney-chromium left a comment (w3ctag/design-reviews#1120)

In reply to https://github.com/w3ctag/design-reviews/issues/1120#issuecomment-3790677450

The MDN entry for `::search-text` has been written and explicitly discusses contrast issues with links and advice on how to test your site. I would expect that has some impact on developers hoping to use the feature.

Find-in-page is a UA feature that some sites aim to circumvent. Some UAs provide better interfaces for presenting the results, and one could certainly push for browser vendors to improve their UI. At some point I got the colors for Chrome's find-in-page ticks changed to improve contrast, but obviously more can be done as demonstrated by Safari (though I personally found their UI somewhat confusing).

Having said that, many sites choose to capture Ctrl-F and implement their own search functionality. I believe that most users would not be able to explain the distinction between the page's search box and the browser UI search box, particularly since only one is displayed if you hit Ctrl-F in most cases (or both present would be even more confusing). Pages may choose this route to improve contrast or the user's search experience.

So I guess it's both a page and UA feature.

Other UA features may also be styled by CSS: spell check result, grammar results and text-fragment URL matches.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1120#issuecomment-3897966561
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1120/3897966561@github.com>