LGTM3

On 8/2/23 11:56 AM, Chris Harrelson wrote:
LGTM2 conditioned on landing the spec.

On Wed, Aug 2, 2023 at 12:12 AM Daniel Bratell <bratel...@gmail.com> wrote:

    Ex post facto LGTM1

    Just try to get that spec updated so that developers will know
    what to expect.

    /Daniel


    On 2023-08-02 00:32, 'Fergal Daly' via blink-dev wrote:
    On Tue, 1 Aug 2023 at 23:44, Mike Taylor <miketa...@chromium.org>
    wrote:

        On 8/1/23 7:54 AM, 'Mingyu Lei' via blink-dev wrote:


                Contact emails

        le...@chromium.org, fer...@chromium.org


                Explainer

        None


                Specification

        None
        Given that WebKit is shipping this and we would like to, any
        reason to not document this behavior to the Clear-Site-Data spec?


    There's an issue here
    <https://github.com/w3c/webappsec-clear-site-data/issues/73>.
    Hopefully we can update the spec shortly,

    F


                Summary

        When performing browsing data removal (e.g. via
        chrome://settings/clearBrowserData, hard reload, or the
        `Clear-Site-Data ` header), the disk and in-memory cache for
        the HTTP response will be cleared. In addition to this, if
        the browsing data removal's data type is "cache", then all
        the BFCache entries matching the origin will be cleared as well.



                Blink component

        UI>Browser>Navigation>BFCache
        
<https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EBrowser%3ENavigation%3EBFCache>


                Search tags

        bfcache <https://chromestatus.com/features#tags:bfcache>


                TAG review

        None


                TAG review status

        Not applicable


                Risks



                Interoperability and Compatibility

        None



        /Gecko/: N/A
        (https://bugzilla.mozilla.org/show_bug.cgi?id=1671182)
        Firefox has removed the cache type data removal for
        Clear-Site-Data header.

        /WebKit/: Shipped/Shipping
        (https://github.com/WebKit/WebKit/pull/4617)

        /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, Chrome OS, 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>?

        No


                Flag name on chrome://flags

        None


                Finch feature name

        None


                Non-finch justification

        The feature has already been released.



                Requires code in //chrome?

        False


                Tracking bug

        https://crbug.com/1428640


                Estimated milestones

        Shipping on desktop     115

        Shipping on Android     115



                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).

        https://github.com/w3c/webappsec-clear-site-data/issues/73


                Link to entry on the Chrome Platform Status

        https://chromestatus.com/feature/5096684790480896

        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+unsubscr...@chromium.org.
        To view this discussion on the web visit
        
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN_fHtn%3DJ5E7Hdcpv9Ojyhrf0AUdoL3PY%3DJxq7jByp5O5pPNgw%40mail.gmail.com
        
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN_fHtn%3DJ5E7Hdcpv9Ojyhrf0AUdoL3PY%3DJxq7jByp5O5pPNgw%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 on the web visit
    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAozHLk7H%2BeZS3WH4ZuicW3oDsadWTg6CYc_0pFXhM7aJdxU5w%40mail.gmail.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAozHLk7H%2BeZS3WH4ZuicW3oDsadWTg6CYc_0pFXhM7aJdxU5w%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 on the web visit
    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5f493d03-bd3c-6e93-8d5f-d7e7c9ac8821%40gmail.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5f493d03-bd3c-6e93-8d5f-d7e7c9ac8821%40gmail.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 on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3b548e4b-f5e4-1ecc-bf43-72235b52c19a%40chromium.org.

Reply via email to