On 3/11/25 5:48 AM, 'Munira Tursunova' via blink-dev wrote:
Contact emails
moon...@google.com, andr...@chromium.org
Explainer
None
Specification
https://drafts.csswg.org/css-values-5/#attr-notation
Summary
In
https://github.com/w3c/csswg-drafts/issues/11645#issuecomment-2701601350
it was resolved to replace `string` attr() type with `raw-string`,
see: https://drafts.csswg.org/css-values-5/#attr-notation. Change
attr() syntax, so that `attr(data-foo string)` will now become
`attr(data-foo raw-string)`.
Blink component
Blink>CSS
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22>
TAG review
None
TAG review status
Pending
Risks
Interoperability and Compatibility
Feature was launched recently in M133 and not supported in other
browsers yet, so shouldn't be a high risk.
Do we have any sense of current usage? And do we have a plan to
communicate the change to developers?
/Gecko/: No signal
/WebKit/: No signal
/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
This is minor syntax change, doesn't require additional support from
DevTools
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
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
https://wpt.fyi/results/css/css-values/attr-all-types.html?label=master&label=experimental&aligned&q=css%2Fcss-values%2Fattr-all-types.html
<https://wpt.fyi/results/css/css-values/attr-all-types.html?label=master&label=experimental&aligned&q=css%2Fcss-values%2Fattr-all-types.html>
Flag name on about://flags
CSSAttrRawString
Finch feature name
CSSAttrRawString
Requires code in //chrome?
False
Tracking bug
https://crbug.com/400981738
Estimated milestones
Shipping on desktop 136
Shipping on Android 136
Shipping on WebView 136
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/5191129693421568?gate=5126282800791552
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 visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_AkzsbO_zudgyt%3DYy6dBp2OKYcgSZZ2UHnUou0--o8Phg%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_AkzsbO_zudgyt%3DYy6dBp2OKYcgSZZ2UHnUou0--o8Phg%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 blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f09c8ebb-f7a6-4843-a221-f85fb48cbf78%40chromium.org.
