Intent to Ship: @property support <string> syntax

[Chromestatus]

Contact emails

moo...@google.com, and...@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 (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/5083057057693696?gate=5140833897283584

This intent message was generated by Chrome Platform Status.

[Rune Lillesveen]

On Thu, Sep 5, 2024 at 1:44 PM Chromestatus <ad...@cr-status.appspotmail.com> wrote:

Contact emails

moo...@google.com, and...@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.

This is also the case for registerProperty(), right?

--

Rune Lillesveen

[Munira Tursunova]

This is also the case for registerProperty(), right?

Right, thanks!

[Mike Taylor]

LGTM1

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_BcN%3Djo2yVEu8w93RXgTqOms%3DQMVY63NkOdDpR70Q_RMA%40mail.gmail.com.

[Yoav Weiss (@Shopify)]

On Tuesday, September 10, 2024 at 5:08:33 PM UTC+2 Mike Taylor wrote:

LGTM1

On 9/5/24 8:40 AM, 'Munira Tursunova' via blink-dev wrote:

This is also the case for registerProperty(), right?

Right, thanks!

On Thu, Sep 5, 2024 at 2:20 PM Rune Lillesveen <fut...@chromium.org> wrote:

On Thu, Sep 5, 2024 at 1:44 PM Chromestatus <ad...@cr-status.appspotmail.com> wrote:

Contact emails moo...@google.com, and...@chromium.org

Explainer None

Specification https://drafts.css-houdini.org/css-properties-values-api-1/#supported-names

The link is 504ing on me. Any alternative path? 

Summary

Support for "<string>" syntax component name in @property.

This is also the case for registerProperty(), right?

--

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 blink-dev+unsubscribe@chromium.org.

[Munira Tursunova]

Latest published version doesn't include <string> as a valid syntax for custom property registration: (https://www.w3.org/TR/css-properties-values-api-1/#supported-names), but I also found a PR with the spec change that adds <string> syntax support for registered custom properties (https://github.com/w3c/css-houdini-drafts/pull/1104). Will this work?

[Mike Taylor]

The server seems to be working now, FWIW.

[Daniel Bratell]

LGTM2

I note that WebKit just very recently landed this so I don't know if it's in production yet.

/Daniel

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5c50efe5-df58-4778-a7b7-7b402c43e777%40chromium.org.

[Chris Harrelson]

LGTM3

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/764abcd9-8f3a-47e7-8664-419d0d6c175d%40gmail.com.