> > Do you have any sense of the relative impact of the breakage for each > site, i.e., does some text look funny (low) vs the page is unusable due to > broken layout or missing content (high)?
I assume theoretically there might be missing content, so high. Is there someone on your team that might be able to attempt outreach to get > these sites to update? Bramus kindly agreed to help with this. Why would we change this? We backed the original intent with the usual > conditions: once the concrete is poured, it's done. I'm not inclined to > approve. There was a spec change initially raised by Apple <https://github.com/w3c/csswg-drafts/issues/11645> after shipping in Blink. I guess we can mention that we wouldn't ship that in Chrome in the CSSWG issue, but I'm not sure if Apple will also ship `string` instead of `raw-string`, which may cause interoperability issues. On Mon, Mar 17, 2025 at 7:21 PM Alex Russell <slightly...@chromium.org> wrote: > Why would we change this? We backed the original intent with the usual > conditions: once the concrete is poured, it's done. I'm not inclined to > approve. > > Best, > > Alex > > On Monday, March 17, 2025 at 8:28:20 AM UTC-7 Mike Taylor wrote: > >> Thank you for looking into that. Do you have any sense of the relative >> impact of the breakage for each site, i.e., does some text look funny (low) >> vs the page is unusable due to broken layout or missing content (high)? >> >> Is there someone on your team that might be able to attempt outreach to >> get these sites to update? >> On 3/17/25 10:49 AM, Munira Tursunova wrote: >> >> Thank you, Bramus and Mike. >> >> >>> That sounds promising, but do we have any UseCounter data? >> >> >> No, but there is some data gathered from http archive: 'string' type in >> attr() >> <https://docs.google.com/document/d/1xrREMWVQiQbDr6OvALHvBko7hokpM44nTPxzEGE7PSs/edit?usp=sharing>. >> I found *15* websites that might cause a potential breakage, so the >> overall percentage of breakages is under *0,000088%*. >> >> >> On Fri, Mar 14, 2025 at 6:21 PM Mike Taylor <miketa...@chromium.org> >> wrote: >> >>> >>> On 3/14/25 7:00 AM, Bramus Van Damme wrote: >>> >>> >>> >>> On Thursday, March 13, 2025 at 7:09:03 PM UTC+1 Mike Taylor wrote: >>> >>> On 3/11/25 5:48 AM, 'Munira Tursunova' via blink-dev wrote: >>> >>> Contact emails moo...@google.com, and...@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? >>> >>> >>> Usage of `attr(data-x string)` seems pretty much inexistent because: >>> >>> - This is Chrome-first and so far I’ve only seen a limited set of demos >>> (that do not even use string). >>> - When a type is omitted - i.e. when using `attr(data-x)` – it behaves >>> like `attr(data-x raw-string)`. The short for is what authors have been >>> using so far. >>> >>> That sounds promising, but do we have any UseCounter data? >>> >>> >>> As for communication I have prepared a PR to update MDN: >>> https://github.com/mdn/content/pull/38580 which is awaiting review. The >>> blog post + demos on developer.chrome.com (See >>> https://developer.chrome.com/blog/advanced-attr) do not mention >>> `attr(data-x string)` as the post points to MDN for docs. I can add an >>> update banner to the post. >>> >>> Thanks for that. >>> >>> >>> >>> >>> >>> *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 >>> >>> >>> 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+...@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/CAAO7W_B%2BSEHACc66Born4zZgp0XdUGNwWU642j9qsxzYZWbBWw%40mail.gmail.com.
