Repro:

• as a user I navigate to https://angular.io and stick around enough for sw to catch everything
• Angular developers push an update to the angular.io homepage (e.g. new release announcement)
• as a user I go to https://blog.angular.io and find a release announcement, I click on a link to https://angular.io/events that is mentioned in the blog post because of new events coming up

Expected result:

• I see the updated version of https://angular.io/events

Current result:

• I see an outdated version of https://angular.io/events
• If I wait long enough for sw to update and reload https://angular.io/events I see the new content

The tricky thing about this is that we shouldn't do it in a way where it's going to affect our TTI.

The new sw has a feature where we can optimize for freshness, but that affects TTI.

Maybe we should consider a full page reload if we detect that the currently displayed content is stale? I'm not sure...

// @alxhub @StephenFluin