Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drop 'potential-navigation-or-subresource request'. #1486

Merged
merged 1 commit into from
Dec 13, 2019
Merged

Drop 'potential-navigation-or-subresource request'. #1486

merged 1 commit into from
Dec 13, 2019

Commits on Nov 25, 2019

  1. Drop 'potential-navigation-or-subresource request'. 

    https://github.com/whatwg/fetch/pull/948/files is changing `<embed>` and `<object>` requests to
look more like navigations than subresource requests. As a result, it seems reasonable for service
worker to explicitly carve out those request destinations which have behavior service worker cares
about, rather than relying on a fetch-level concept that doesn't make sense in the new model.
    @mikewest
    mikewest authored Nov 25, 2019
    Configuration menu
    Copy the full SHA
    33abec1 View commit details
    Browse the repository at this point in the history