Intent to Ship: CSS Custom Highlight Universal Selector ::highlight(*)

155 views
Skip to first unread message

Chromestatus

unread,
Oct 14, 2026, 5:02:55 AMOct 14
to blin...@chromium.org, re...@igalia.com, sche...@igalia.com, seo...@chromium.org
Contact emails
seo...@chromium.org

Explainer
No information provided

Specification
https://drafts.csswg.org/css-pseudo-4/#selectordef-highlight-highlight-name-selector

Summary
Introduces a universal selector for custom highlights, ::highlight(*), which matches the highlight pseudo-elements of all custom highlights regardless of their name. The * argument contributes zero specificity, so its declarations act as a base style that rules naming a specific highlight override through the cascade.

Blink component
Blink>CSS

Web Feature ID
Missing feature

Motivation
Styling shared properties across custom highlights requires repeating the same declarations for every registered name. The CSSWG resolved to allow ::highlight(*).

Initial public proposal
https://github.com/w3c/csswg-drafts/issues/9091

Search tags
Custom Highlight

TAG review
No information provided

TAG review status
Pending

Goals for experimentation
None

Risks


Interoperability and Compatibility
No information provided

Gecko: Under consideration (https://github.com/mozilla/standards-positions/issues/1460)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/728)

Web developers: No signals

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?

No information provided


Debuggability
No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by web-platform-tests?
Yes


Flag name on about://flags
No information provided

Finch feature name
No information provided

Non-finch justification
No information provided

Rollout plan
Will ship enabled for all users

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/408003366

Estimated milestones
Shipping on desktop158
Shipping on Android158
Shipping on WebView158


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

No information provided

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5174965228929024?gate=6101897755885568

Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a7e62a2.2164c308.b1fa7.0128.GAE%40google.com


This intent message was generated by Chrome Platform Status.

Alex Russell

unread,
Oct 14, 2026, 11:21:42 AMOct 14
to blink-dev, Chromestatus, Manuel Rego, sche...@igalia.com, Seokho Song
As discussed at API OWNERS, it seems strange that we don't have any developer interest for this. Presumably folks are asking for this, right?

Seokho Song

unread,
Oct 14, 2026, 8:52:07 PMOct 14
to blink-dev, Alex Russell, Chromestatus, Manuel Rego, sche...@igalia.com, Seokho Song
Hi Alex. 

Yes, there’s been interest. Signals so far:

Additionally, Mozilla engineers emilio and jnjaeschke consider it reasonable in the standards-positions issue.


Alex Russell

unread,
Oct 19, 2026, 2:22:38 PMOct 19
to blink-dev, Seokho Song, Alex Russell, Chromestatus, Manuel Rego, sche...@igalia.com
Thank you for giving us a sense of the demand. LGTM1.

Dan Clark

unread,
Oct 19, 2026, 2:23:00 PMOct 19
to blink-dev, sligh...@chromium.org, seo...@chromium.org, Chromestatus, Manuel Rego, sche...@igalia.com
LGTM2

Mike Taylor

unread,
Oct 19, 2026, 9:01:55 PMOct 19
to Dan Clark, blink-dev, sligh...@chromium.org, seo...@chromium.org, Chromestatus, Manuel Rego, sche...@igalia.com

LGTM3

--
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+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dd7f5241-790c-40d9-89c2-a47564a95639n%40chromium.org.
Reply all
Reply to author
Forward
0 new messages