LGTM2

/Daniel

On 2024-07-03 13:53, Yoav Weiss (@Shopify) wrote:
LGTM1

On Wed, Jul 3, 2024 at 1:50 PM Anders Hartvoll Ruud <[email protected]> wrote:

    On Wed, Jul 3, 2024 at 11:35 AM Yoav Weiss (@Shopify)
    <[email protected]> wrote:



        On Wednesday, July 3, 2024 at 10:47:21 AM UTC+2 Anders
        Hartvoll Ruud wrote:

            Contact [email protected]

            ExplainerNone

            
Specificationhttps://drafts.csswg.org/css-anchor-position-1/#position-try-fallbacks
            
<https://drafts.csswg.org/css-anchor-position-1/#position-try-fallbacks>

            Summary

            Replaces the inset-area() function with inset-area values
            directly within position-try-fallbacks. This means that
            you now just write e.g. position-try-fallbacks:top instead
            of position-try-fallbacks:inset-area(top).


        Just to clarify - this removes the inset-area function?


    Yes, correct.


            The CSSWG made this change shortly after CSS Anchor
            Positioning shipped in Blink:

            
https://github.com/w3c/csswg-drafts/issues/10320#issuecomment-2137882897
            
<https://github.com/w3c/csswg-drafts/issues/10320#issuecomment-2137882897>



            Blink componentBlink>CSS
            
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>

            TAG reviewNone

            TAG review statusNot applicable

            Risks


            Interoperability and Compatibility


            Searching for existing cases of "inset-area(" in HTTP
            Archive, I found just a single match out of 638589186 rows:

            https://css3test.com/tests/css-anchor-position-1.js
            <https://css3test.com/tests/css-anchor-position-1.js>


        Do you know if this was used in a production site?
        From the name, one can assume it's a demo site..

    It's just the input for the view to show the features supported by
    the browser e.g.: https://css3test.com/#css-anchor-position-1

    It doesn't count as "production use" IMO. Also, I sent a PR to
    update it: https://github.com/LeaVerou/css3test/pull/249


Agree!



            Query used:

            #standardSQL

            SELECTresponse_bodies.url

            
FROM`httparchive.response_bodies.2024_06_01_desktop`ASresponse_bodies

            WHEREREGEXP_CONTAINS(response_bodies.response_body,
            r'inset\-area\(')


            /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)?No

            Is this feature fully tested by web-platform-tests
            
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?Yes

            Flag name on chrome://flagsNone

            Finch feature nameCSSInsetAreaValue

            Requires code in //chrome?False

            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/5116199771045888?gate=5071381116223488
            
<https://chromestatus.com/feature/5116199771045888?gate=5071381116223488>

            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/CAOmohS%2Ba%2BW6mFB9LLuu5eh6HwLg%2BHu7HxzoH-p73%2B38MnGSiyg%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2Ba%2BW6mFB9LLuu5eh6HwLg%2BHu7HxzoH-p73%2B38MnGSiyg%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/65a95f8b-ac2c-42dd-b016-0a0c44b0e55c%40gmail.com.

Reply via email to