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

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

Thanks for the feedback and the time you've spent reviewing.

I'll address the potential for abuse first. I feel there are easier ways for a page to be abusive than messing with find-in-page (and pages can already completely capture the keyboard shortcuts for find-in-page). For example, authors can set transparent background-color for selection styling, removing feedback of what has been selected. It's clearly bad for users when there is no feedback of selected content, but all browsers allow it and have for a long time. 

You raise a very good point regarding various color-modifying settings, like CSS forced-colors and prefers-reduced-contrast. We should amend the proposal to say those settings override author defined colors, as they do for things like caret color and selection.

I have considered the "modify the colors based on contrast assessment" and the challenge is determining what the background is.  In most cases it's tricky, let alone if a background image is present. I believe that's the motivation for Safari's  overlay under the results to eliminate background influence. I think to make an automated contrast approach work the other browsers would need to implement something like Safari, which was actually a proposal raised in the Blink Intent to Ship process.

In response to all this I will update the explainer with the alternatives proposed here, restart the Blink Intent discussion, and talk to the people involved in the CSS spec issue. Hopefully some consensus can be reached.

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

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