@slightlylate hey Alex. Any suggestions on this by any chance? Not quite sure what the best way would be to go about this, I'd appreciate your input if you have time:https://twitter.com/HenrikJoreteg/status/1012400177569673219 …
-
-
Replying to @HenrikJoreteg
Delaying activation is interesting. Today, that's accomplished by keeping a client (window/tab) around and enabling you to bail out of installation by throwing an error in the `install` event.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @HenrikJoreteg
I'd be using the install event rejection to make this happen, as you'd still be able to do things like prep the caches for the next version to take over at some future point. Because versions can "see" each other, you can ping the active version to ask "is now a good time?"
1 reply 0 retweets 1 like -
Replying to @slightlylate
hm... that's really interesting. I'm trying to make sure I understand you. So you're saying the install event, you'd intentionally throw an error if it wasn't a good time?
1 reply 1 retweet 0 likes -
Replying to @HenrikJoreteg
Correct. You'd feed a rejection to the waitUntil promise at the very end of the chain.
2 replies 1 retweet 0 likes -
Replying to @slightlylate @HenrikJoreteg
Perhaps we missed a trick in the design, but the general principle is that only the next version is compos mentis regarding the previous version.
1 reply 0 retweets 0 likes
So your choices as the newer version are vast; your choices as the previous version are negligible.
/cc @jaffathecake
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.