Good stuff by @dfabu on the SW lifecycle: https://redfin.engineering/service-workers-break-the-browsers-refresh-button-by-default-here-s-why-56f9417694 …
I often can tell how mature an engineer is by how freaked out they are by what SWs let you break ;-)
-
-
Replying to @slightlylate
I just published the second part of my guide to the Service Worker lifecycle, explaining how to fix the browser's Refresh button when SWs break it.https://redfin.engineering/how-to-fix-the-refresh-button-when-using-service-workers-a8e27af6df68 …
4 replies 9 retweets 25 likes -
Replying to @dfabu
s/break it/put you in control, exactly the way you requested when adding a client-side proxy/
1 reply 0 retweets 0 likes -
Replying to @slightlylate
ennnnh, in the case of refreshing the last/only tab, I think it's a flaw in the design that it doesn't skipWaiting before loading the new page. It's a bad default, not just "too much control"
1 reply 0 retweets 0 likes -
Replying to @dfabu @slightlylate
I understand why the design is the way it is, but I feel that the design forces developers to write a lot of code (and understand a lot of high concepts) to opt-in to sane behavior
1 reply 0 retweets 0 likes -
Replying to @dfabu
Well, the default behaviour is "sane", in the sense that it doesn't incidentally break your app's behaviour with new versions. Doing more sophisticated thing requires more knowledge. This is the Extensible Web in action.
2 replies 0 retweets 0 likes
For that specific issue, we tried the other way, but `content-disposition` 


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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.