- From: Jihye Hong <notifications@github.com>
- Date: Mon, 14 Jul 2025 08:51:27 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1120@github.com>
jihyerish created an issue (w3ctag/design-reviews#1120) ### Specification https://drafts.csswg.org/css-pseudo-4/#selectordef-search-text ### Explainer https://github.com/Igalia/explainers/blob/main/css/find-in-page/README.md ### Links - An introduction to the feature, aimed at unfamiliar audiences: https://github.com/Igalia/explainers/blob/main/css/find-in-page/README.md - A description of the problems that end-users were facing before this proposal: https://stackoverflow.com/questions/50309703/css-for-browsers-find-in-page - Examples of how to use the proposal to solve the end-users' problems: https://github.com/Igalia/explainers/blob/main/css/find-in-page/README.md#example - What do the end-users experience with this proposal: https://github.com/Igalia/explainers/blob/main/css/find-in-page/README.md#risks - Web Platform Tests: third_party/blink/web_tests/wpt_internal/css/css-pseudo/search-text-* ### The specification - [ ] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/). - [ ] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/). ### Where and by whom is the work is being done? - GitHub repo: https://github.com/Igalia/explainers/tree/main/css/find-in-page - Primary contacts: - Delan Azabani (@delan), Igalia - Jihye Hong (@jihyerish), Igalia - Stephen Chenney (@schenney-chromium), Igalia - Organization/project driving the specification: Igalia - This work is being funded by: Bloomberg and Igalia - Primary standards group developing this feature: CSSWG - Incubation and standards groups that have discussed the design: - https://github.com/w3c/csswg-drafts/issues/3812 This is the initial idea of this feature. After several discussions, the syntax has been changed ### Feedback so far - Multi-stakeholder feedback: - Chromium comments: Positive, https://chromestatus.com/feature/5195073796177920 - Mozilla comments: https://github.com/mozilla/standards-positions/issues/1103 - WebKit comments: https://github.com/WebKit/standards-positions/issues/421 - Status/issue trackers for implementations: [Chromium](https://issues.chromium.org/issues/339298411) ### You should also know that... _No response_ <!-- Content below this is maintained by @w3c-tag-bot --> --- Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1120 -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1120 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1120@github.com>
Received on Monday, 14 July 2025 15:51:31 UTC