Contact emailsjar...@chromium.org ExplainerNone
Specificationhttps://github.com/whatwg/html/pull/8467 Summary CSS custom state, which allows custom elements to expose their own pseudo-classes, was shipped here: https://groups.google.com/a/chromium.org/g/blink-dev/c/dJibhmzE73o/m/VT-NceIhAAAJ This feature has not been implemented in gecko or webkit yet. I recently made an effort to spec this feature in CSSWG and WHATWG, but there was pushback to change the syntax back from :--foo to :state(foo), and the CSSWG has resolved to do this as well: https://github.com/w3c/csswg-drafts/issues/4805 The UseCounter is currently at 0.03% https://chromestatus.com/metrics/feature/timeline/popularity/3796 This deprecation will have a window where we support both the old syntax and the new syntax so websites can switch to the new one. Blink componentBlink>HTML>CustomElements <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHTML%3ECustomElements> TAG reviewNone TAG review statusNot applicable Risks Interoperability and Compatibility Websites which are currently using the old syntax and don't migrate to the new syntax will have CSS selectors which become invalid which would impact the styling of their custom elements. *Gecko*: No signal *WebKit*: No signal ( https://github.com/whatwg/html/pull/8467#issuecomment-1381645661) *Web developers*: No signals *Other signals*: Activation Switching to the new syntax should be quite easy. 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 Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Flag name on chrome://flagsNone Finch feature nameNone Non-finch justificationNone Requires code in //chrome?False Estimated milestones No milestones specified 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). None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5140610730426368 This intent message was generated by Chrome Platform Status <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/CAK6btw%2BkfRmmERKWTK5XayiuWHTpo3AhTJjhrWrdL8_QDxigZg%40mail.gmail.com.
