LGTM3 - I agree that those local peaks are not scary enough so this should be ok to ship.

(This might be a duplicate but I'm not going to wait any longer for my first mail to arrive!)

/Daniel

On 2022-06-22 17:56, Mike Taylor wrote:
LGTM2

On 6/22/22 11:56 AM, Chris Harrelson wrote:
LGTM1

On Thu, Jun 16, 2022 at 11:38 AM Johann Hofmann <[email protected]> wrote:

    Thanks everyone, a quick update:

    Thank you Martin for chiming in, I really appreciate your
    comment! I updated the Chromestatus entry to reflect the browser
    signals more accurately.

    I also sent a request for position
    <https://lists.webkit.org/pipermail/webkit-dev/2022-June/032306.html>
    to webkit-dev.

    Addressing Mike's and Daniel's concern about localized hot spots
    (sorry for the delay):

    Looking at global usage data, it seems to be consistently low in
    all countries. There are some regional differences, with Brazil,
    Croatia and Belarus having slightly elevated usage at 0.2%, all
    likely subject to randomness/noise as we're looking at a very
    small subset of data at this point. We might be able to find out
    more about those during deprecation, but overall I'm not very
    concerned.

    Thanks!

    Johann

    On Thu, Jun 9, 2022 at 1:49 AM Daniel Bratell
    <[email protected]> wrote:


        On 2022-06-09 04:22, Martin Thomson wrote:
        On Wed, Jun 8, 2022 at 10:55 PM Daniel Bratell
        <[email protected]> wrote:

            If Mozilla is already shipping this behaviour, then
            there is no need to ask them if they support that
            change. We do assume that they approve of all
            functionality they are shipping.

        I want to address this point, as I think Chris Harrelson has
        done.  Just because something ships in Firefox, that doesn't
        mean we think that it is good for the web.  There's
        something of a long list of things we don't like, but ship
        for various reasons despite that.  To pick an example that
        isn't particularly controversial, we still ship unsecured HTTP.

        So we do appreciate you asking directly rather than making
        inferences and then potentially misrepresenting our position.

        To save a bit of time on this bit of minutiae: this change
        is good and the work that Johann, Mike, and others on the
        Chrome team have done to improve compatibility with cookies
        is greatly appreciated.

        Correction appreciated! I was way too cavalier with that
        statement.

        /Daniel

-- 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/CAD_OO4hs%2BgbCuXxWgOmVoVQ9zv9hRnnKYwi%2BMS9ciX76%3DVD%2Buw%40mail.gmail.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAD_OO4hs%2BgbCuXxWgOmVoVQ9zv9hRnnKYwi%2BMS9ciX76%3DVD%2Buw%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/d331ba4c-593a-f7f6-ad28-4c42c991b05d%40gmail.com.

Reply via email to