LGTM3 On Wednesday, October 11, 2023 at 4:08:02 PM UTC+2 Mike Taylor wrote:
> LGTM2 > On 10/11/23 7:06 AM, Daniel Bratell wrote: > > LGTM1 > > (Privacy and Security steps in Chromestatus are not completed but they are > unlikely to affect anything) > > /Daniel > On 2023-10-04 12:23, Rune Lillesveen wrote: > > > > On Wed, Oct 4, 2023 at 11:08 AM Rune Lillesveen <[email protected]> > wrote: > >> Contact emails [email protected], [email protected] >> >> Explainer None >> >> Specification >> https://drafts.css-houdini.org/css-properties-values-api-1/#syntax-strings >> >> Summary >> >> Supports using the <image> syntax for custom properties registered with >> @property or registerProperty(). The <image> syntax can be used to restrict >> values of the custom property to url() values and generated images like >> gradients. >> >> >> This syntax was initially excluded from the valid syntaxes mainly because >> images were not interpolable and that it would add to the usefulness of the >> syntax to be able to interpolate directly on the custom property. The other >> engines have shipped the image syntax without supporting interpolation. >> There are two interpolation methods in css-image-4, cross-fade() and per >> stop interpolation for gradients. The gradient interpolation is not shipped >> by any browser (even for standard properties). Safari ships a non-standard >> compliant cross-fade() interpolation for standard properties (at least for >> background-image), but not for the registered custom properties. >> >> >> We have an OKR to look into cross-fade() for Q4. If we end up shipping >> that, it will work for both registered custom properties and standard >> properties. >> >> >> The <image> syntax for registered custom properties is part of Interop >> 2023. >> >> >> Blink component Blink>CSS >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> >> >> TAG review None >> >> TAG review status Not applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: Shipped/Shipping Does not support interpolation >> > > Sorry, this is not correct. It's implemented behind a flag, not shipping > yet. > > *WebKit*: Shipped/Shipping Does not support interpolation >> >> *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? >> >> None >> >> >> Debuggability >> >> No additional devtools support necessary compared to existing syntaxes. >> >> >> 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 >> >> https://wpt.fyi/css/css-properties-values-api/at-property.html >> https://wpt.fyi/css/css-properties-values-api/register-property-syntax-parsing.html >> >> https://wpt.fyi/css/css-properties-values-api/typedom.html >> >> >> Flag name on chrome://flags #enable-experimental-web-platform-features >> >> Finch feature name CSSVariables2ImageValues >> >> Requires code in //chrome? False >> >> Estimated milestones >> Shipping on desktop 120 >> DevTrial on desktop 115 >> Shipping on Android 120 >> DevTrial on Android 115 >> >> 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/5142205606133760 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- >> Rune Lillesveen >> >> > > -- > Rune Lillesveen > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuPfeRpL_rGG0%2BuaCiozmx6PoShU4H4SY8HaZwCKs8aReKnUg%40mail.gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuPfeRpL_rGG0%2BuaCiozmx6PoShU4H4SY8HaZwCKs8aReKnUg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > 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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b54e692d-f48c-46ed-89d4-962336bda253%40gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b54e692d-f48c-46ed-89d4-962336bda253%40gmail.com?utm_medium=email&utm_source=footer> > . > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7c3a0e0e-203d-4860-a2e2-1dcb7170b8c8n%40chromium.org.
