The offline implementation here is just a simple one that servers a custom offline.html page. Basically, if the browser has support for service workers, the offline.html page is cached on first visit, on repeat visits if the user is not connected to the network, the cached offline.html is served.
The offline implementation here is just a simple one that servers a custom offline.html page. Basically, if the browser has support for service workers, the offline.html page is cached on first visit, on repeat visits if the user is not connected to the network, the cached offline.html is served.
Hope that helps :)