Contact emails moon...@google.com, andr...@chromium.org
Explainer None Specification https://drafts.css-houdini.org/css-properties-values-api-1/#supported-names Summary Support for "<string>" syntax component name in @property. Blink component Blink>CSS TAG review None TAG review status Pending Risks Interoperability and Compatibility None, already shipped in Firefox and Safari. Gecko: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=1846635) WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=277655) Web developers: No signals Other signals: Ergonomics N/A Activation N/A Security N/A 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 No DevTools debugging support needed. The feature is observable in DevTools same way as other supported syntax component names. 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 wpt/css/css-properties-values-api/at-property.html wpt/css/css-properties-values-api/register-property-syntax-parsing.html Flag name on chrome://flags Finch feature name CSSAtPropertyStringSyntax Requires code in //chrome? False Tracking bug https://g-issues.chromium.org/issues/357751736 Estimated milestones Shipping on desktop 131 Shipping on Android 131 Shipping on WebView 131 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (eg links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (eg, 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/5083057057693696?gate=5140833897283584 This intent message was generated by Chrome Platform Status. -- 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/0000000000004eb44a06215dd0d2%40google.com.