On Wed, Jul 3, 2024 at 11:17 AM Anders Hartvoll Ruud <[email protected]> wrote:
> I'll answer since Mason is now OOO. > > On Tue, Jul 2, 2024 at 8:48 AM Yoav Weiss (@Shopify) < > [email protected]> wrote: > >> >> >> On Tuesday, July 2, 2024 at 12:38:50 AM UTC+2 Mason Freed wrote: >> >> Contact [email protected], [email protected] >> >> Specificationhttps://github.com/w3c/csswg-drafts/issues/10395# >> issuecomment-2192127524 >> >> Summary >> >> The CSSWG resolved to rename this property, because "fallbacks" more >> accurately describes what this property controls. The word "options" is a >> bit deceiving, since the styles outside of `position-try` blocks will be >> tested first, and if they result in a layout that fits within the >> containing block, none of the "options" will get used. So "fallbacks" is a >> better word to describe this behavior. https://github.com/w3c/csswg- >> drafts/issues/10395#issuecomment-2192127524 >> >> >> Blink componentBlink>CSS >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> >> >> Search tagsanchor positioning >> <https://chromestatus.com/features#tags:anchor%20positioning> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> This is a name change, which will result in the old name no longer >> functioning. So there is a risk of breakage. However, the anchor >> positioning feature was very recently shipped, and does not have >> implementation in other browsers. So we feel the risk is quite small >> currently, but will grow over time. Given that, we'd like to rename this >> property ASAP to avoid the risk getting too large. The use counter is >> currently quite low, around 0.01% in June: https://chromestatus.com/ >> metrics/css/timeline/popularity/784 An HTTP Archive search was >> performed, which showed that almost all usage comes from one Shopify CSS >> file (`spec-and-compare.css`), and we intend to reach out to Shopify (or >> hope for a response from one very special Blink API owner) to make sure >> this will not break Shopify. >> >> >> "very special" :) >> >> It seems like the source of usage is this 3P app: >> https://apps.shopify.com/spec-compare >> I'll send you their contact email so that you can reach out to them >> directly. >> > > Note: They can preemptively handle this change today by using > position-try:flip-inline instead. > > >> >> Can you share the HTTP Archive analysis? Manual inspection of the hosts >> listed in the chromestatus counter didn't reveal much on my end. >> > > Not sure about "analysis", but the raw dump is here: > https://docs.google.com/document/d/1x3JKq_iGv24w-2y-rzQbS6MV78UcsTH1yWEJFeH-RdY/edit?usp=sharing > (@chromium.org to access) > > It looks like the usage we see from HTA so far is flip-block/flip-inline, > which e.g. means a tooltip won't move over to the other (better) side of a > box when it's scrolled out of view. > > Beyond that, I think this would require an intent and maybe a short >> deprecation period. Even if the only source is this single app, unless the >> breakage is insignificant, >> > we'd need at least one release overlap between the new and the old values, >> to avoid a breakage period while users are upgrading from Chromium N to N+1. >> > > It's tricky, because waiting could actually cause *more* breakage, even > with a deprecation period, and the numbers look quite good right now. > If the app in question could switch to `position-try:flip-inline` that changes things, and would indeed not require a milestone overlap, assuming they can make that change. > >> >> >> >> *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 >> >> None >> >> >> 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-anchor-position >> >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justificationNone >> >> Requires code in //chrome?False >> >> Tracking bughttps://crbug.com/349600667 >> >> Estimated milestonesShipping on desktop128Shipping on Android128Shipping >> on WebView128 >> >> 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 Statushttps://chromestatus.com/ >> feature/5167414571696128?gate=5182169462079488 >> >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cf8a8c9d-9efa-4bff-9dd5-590809fe2877n%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cf8a8c9d-9efa-4bff-9dd5-590809fe2877n%40chromium.org?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/CAOmohSLQxbs-ZsMncyC%3DVeXSx5%2BtU7rY9Vg3wC4LU-Rh6Vdx2Q%40mail.gmail.com.
