Contact emails schen...@chromium.org, dazab...@igalia.com Explainer https://github.com/Igalia/explainers/blob/66623464ba1f2410a130d687116302b4a30b1148/css/find-in-page/README.md [1] Specification None yet; to be specified in https://drafts.csswg.org/css-pseudo/#highlight-pseudos [2] Summary Exposes find-in-page search results to authors as a highlight pseudo-element, like selections and spelling errors. This allows authors to change the foreground and background colors or add text decorations, which can be especially useful if the UA defaults have insufficient contrast with the page colors or are otherwise unsuitable. Blink component Blink>CSS [3] Motivation Authors would like to customize the highlighted text from find-in-page to have a style consistent with that of the rest of the page. In particular, the existing find-in-page highlights may offer poor contrast, harming accessibility. The find-in-page highlights may also conflict with other highlights on the page, such as syntax highlighting. Initial public proposal https://github.com/w3c/csswg-drafts/issues/3812 [4] Search tags search [5] TAG review None TAG review status Pending
RISKS Interoperability and Compatibility None _Gecko_: Not yet requested _WebKit_: Not formally requested, but feedback on the CSS WG issue and in meetings. Unlikely to implement due to Safari's unique UI behavior, but not opposed to the spec as long as UAs are allowed to parse but ignore the pseudo. CSS Working Group discussed and is OK with moving forward with prototyping under these conditions. _Web developers_: Resolve problems with choosing code syntax highlighting colors https://github.com/w3c/csswg-drafts/issues/3812#issuecomment-1703272181 [6]; Explicit request for the feature How to style/detect highlighted boxes generated from browser native search in page - Stack Overflow [7]; Another use case Confuse browsers in-built "find in page" feature - Stack Overflow [8] _Other signals_: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability None Is this feature fully tested by web-platform-tests [9]? Not yet; tests will be written during the spec and impl process Flag name on chrome://flags #enable-experimental-web-platform-features SearchTextHighlightPseudo Finch feature name None Non-finch justification None Requires code in //chrome? False Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5195073796177920 [10] This intent message was generated by Chrome Platform Status [11]. Links: ------ [1] https://github.com/Igalia/explainers/blob/66623464ba1f2410a130d687116302b4a30b1148/css/find-in-page/README.md [2] https://drafts.csswg.org/css-pseudo/#highlight-pseudos [3] https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS [4] https://github.com/w3c/csswg-drafts/issues/3812 [5] https://chromestatus.com/features#tags:search [6] https://github.com/w3c/csswg-drafts/issues/3812#issuecomment-1703272181 [7] https://stackoverflow.com/questions/18666075/how-to-style-detect-highlighted-boxes-generated-from-browser-native-search-in-pa [8] https://stackoverflow.com/questions/77458310/confuse-browsers-in-built-find-in-page-feature [9] https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md [10] https://chromestatus.com/feature/5195073796177920 [11] https://chromestatus.com -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c447ed4dfd05b588e2afc650277371fd%40igalia.com.
