HelNershingThapa
commented
1 year ago It appears that the behavior of cached files being served on new tabs, even after performing a hard refresh on the site, is expected behavior in line with my understanding of how service workers work. However, please note that I may be mistaken as I do not have extensive experience with service workers.
As per my analysis, when a service worker is active, a forced refresh will completely avoid it and provide content directly from the network instead. For this reason, when you merely refresh the page, you could see that some assets are delivered by the service worker, however, when you hard refresh the page, the assets are supplied from the network, resulting in the presentation of the most recent assets.
Asset is served from the network on hard refresh:
Asset is served by service worker on new tabs and on normal refresh:
Because the app uses an older service worker and the new service worker hasn't been enabled within that timeframe, the cached content is shown when viewing the same page in a new tab. Although this may give the impression that cached files continue to exist even after a hard refresh of the website, it is actually the result of service workers acting as planned.
Aadesh-Baral
ramyaragupathy
The issue is that after a new update, the service worker for the app is not installing properly and is stuck in the "trying to install" phase. This means that users will not be receiving the latest version of the app, even after performing a hard refresh (Ctrl+Shift+R).
Additionally, while the hard refresh successfully update the current page to the latest version, there is still the previous version of the app being loaded on other pages and in new tabs.
If the user opens a new tab after performing a hard refresh and the service worker is still not installed properly, they may still receive the previous version of the app in the new tab. This is because the browser may use the same service worker instance across different tabs. Therefore, if the service worker is not updated, it will still serve the old version of the app to the user in the new tab.