LGTM2

On 10/8/26 12:25 p.m., Chris Harrelson wrote:
LGTM1

On Thu, Oct 8, 2026, 7:29 AM Nan Lin <[email protected]> wrote:


    On Thursday, October 8, 2026 at 10:26:45 AM UTC-4 Nan Lin wrote:

        Hi API Owners,

        We are requesting approval to proceed with the staged
        deprecation rollout:

          * 10% Stable: Hold for 2 weeks (through Oct 24)
          * 100% Stable: Target launch after Oct 24

        During the initial rollout, we identified a regression
        (https://crbug.com/553155942) where /window.open()/ calls
        using /attributionsrc/ were incorrectly opening in popup
        windows instead of new tabs.
        To fix this, we isolated the /window.open()/ parsing behavior
        from this removal. This fix has been fully verified and rolled
        out to Stable in M155.

        With the /window.open()/ regression fixed, we are not seeing
        any ongoing breakage. While overall usage metrics remain high
        (~12.37% <http://32.248.125.102/>), we believe it is safe to
        proceed.


    Sorry the link to the usage metrics is
    https://chromestatus.com/metrics/feature/timeline/popularity/3365.


        Thank you for your consideration.

        Best,
        Nan

        On Wednesday, July 1, 2026 at 11:34:36 AM UTC-4 Daniel Bratell
        wrote:

            LGTM3 for steps 2 and 3.

            /Daniel

            On 2026-06-26 10:21, Yoav Weiss (@Shopify) wrote:
            LGTM2

            On Thu, Jun 25, 2026 at 11:12 PM Chris Harrelson
            <[email protected]> wrote:

                LGTM1

                On Thu, Jun 11, 2026 at 2:54 PM Nan Lin
                <[email protected]> wrote:

                    Hi API Owners, The Attribution Reporting API was
                    deprecated in Chrome-144 with a plan to remove it
                    in Chrome-150. Currently the usage is 19.7% of
                    page
                    
loads.<https://chromestatus.com/metrics/webfeature/timeline/popularity/282>We
                    are proposing the following as next steps for
                    removal and associated timelines: 1. M150: Remove
                    all Ads API-related entries from Chrome settings
                    and UI surfaces (e.g.,
                    chrome://settings/adPrivacy) via field trial.
                    After this point, all API invocations for
                    field-trial enabled browsers will always reject.
                    Since the API can already be disabled for one of
                    many reasons, scripts must already handle such
                    rejections (or they’re already significantly
                    broken).2. M152: Permanently remove the
                    underlying implementation code for the API, and
                    replace it with a lightweight stub API. The stub
                    will remain removable via field trial.

                    3. M152 Canary/Beta: Begin a controlled rollout
                    of the stub API removal via a field trial.4. M152
                    Stable: Assuming there are no regressions or
                    breakage after reaching 1% stable, we will
                    request additional approval for full removal at
                    this stage.


                    At this time, we are seeking LGTMs for steps #2
                    and #3.


                    Thanks,

                    Nan



-- 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]
                    <mailto:[email protected]>.
                    To view this discussion visit
                    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b0f59039-244a-4ce7-838b-aab7e6ef51abn%40chromium.org
                    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b0f59039-244a-4ce7-838b-aab7e6ef51abn%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]
                <mailto:[email protected]>.
                To view this discussion visit
                
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8JtDZdVUb1kTtNc4dNYPs-3v%3DJwkQU7oWAE6dSchxG1Q%40mail.gmail.com
                
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8JtDZdVUb1kTtNc4dNYPs-3v%3DJwkQU7oWAE6dSchxG1Q%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]
            <mailto:[email protected]>.
            To view this discussion visit
            
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSJqg17LUafnekTwvpeaB2tiUOZaWcHyabB-xxoxr_Y8uQ%40mail.gmail.com
            
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSJqg17LUafnekTwvpeaB2tiUOZaWcHyabB-xxoxr_Y8uQ%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 visit
    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/157961f2-c57a-4671-ba71-7eaae350e49fn%40chromium.org
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/157961f2-c57a-4671-ba71-7eaae350e49fn%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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_odyzbGyjjARfUVF-7Xeez-uqGxL_0%3D3FxDZqHkRyR8A%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_odyzbGyjjARfUVF-7Xeez-uqGxL_0%3D3FxDZqHkRyR8A%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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4fcddf95-c138-42d0-9337-15a15a3afa58%40chromium.org.

Reply via email to