Closed dandclark closed 7 months ago
I think we should exclude some tests that are tentative or not directly related to the highlight API if this were to be included:
Thank you for proposing Custom Highlight API for inclusion in Interop 2024.
We wanted to let you know that this proposal was not selected to be part of Interop 2024. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year, if necessary.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!
Posted on behalf of the Interop team.
Description
The custom highlight API provides a way for web developers to style the text of arbitrary text ranges without wrapping them with additional HTML elements. This is useful in a variety of scenarios, including editing frameworks that wish to implement their own selection, find-on-page over virtualized documents, multiple selections to represent online collaboration, or spellchecking frameworks.
Specification
https://drafts.csswg.org/css-highlight-api-1/
Open Issues
In the future there are plans to make this API more powerful by adding user interaction via PointerEvents integration: https://github.com/w3c/csswg-drafts/issues/7447. See list of open issues here: https://github.com/w3c/csswg-drafts/labels/css-highlight-api-1. These are forward-looking and don't block implementation of the current spec.
Tests
https://wpt.fyi/results/css/css-highlight-api
Current Implementations
Standards Positions
Gecko: Positive Safari: Support
Browser bug reports
No response
Developer discussions
Use cases discussed with some developer commentary here: https://github.com/w3c/csswg-drafts/issues/4307. CKEditor had also shown support from the early days of the highlight API explainer. Supportive comments on https://css-tricks.com/css-custom-highlight-api-early-look/.
Polls & Surveys
No response
Existing Usage
Negligible in Chromium: https://chromestatus.com/metrics/feature/timeline/popularity/3984
Workarounds
No response
Accessibility Impact
No response
Privacy Impact
No response
Other
Gecko and Webkit both have experimental implementations of the feature. Blink is the only one shipping in Stable.