@nzgb @jaffathecake It only hits the service worker again for non-subresource loads. So windows, workers, iframes, etc.
-
-
Replying to @wanderview
@wanderview is this true? Was reviewing@annevk's new redirect stuff, it suggested it'd go back through the SW with subresources1 reply 0 retweets 0 likes -
-
Replying to @jaffathecake
@jaffathecake Yea, I'm wrong. Still haven't looked at that PR, but right now it sets skip-sw only if a SW does *not* respondWith().2 replies 0 retweets 0 likes -
Replying to @wanderview
@jaffathecake So leaving spec unchanged from orig seems like a good option. If using relative css subresources, then .redirect() stylesheet.1 reply 0 retweets 0 likes -
Replying to @wanderview
@wanderview makes me uncomfortable that we're creating differences from standard browser behaviour, but maybe it's ok2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake And quite frankly, standard browser behavior is to use response for base URI everywhere. So already breaking for page case.2 replies 0 retweets 0 likes -
Replying to @wanderview
@wanderview we've never had response.url different to request URL for pages until service worker. The spec doesn't say that's how base works1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake We haven't? Aren't request and response URL different for redirected stylesheet? And spec was quite vague for nav redirects.2 replies 0 retweets 0 likes -
Replying to @wanderview
@jaffathecake But I guess I don't have the history. My impression from@bz_moz and@ehsanakhgari was this happened pre-SW and used response.4 replies 0 retweets 0 likes
@wanderview @jaffathecake @ehsanakhgari Happy to talk about this via IRC, video chat, email, etherpad, or any other sane conversation medium
-
-
Replying to @really_bz
@bz_moz@jaffathecake@ehsanakhgari Afk right now, but the context is: https://jakearchibald.com/2016/service-workers-and-base-uris/ …0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.