___                                           
         _   _        (  _`\                      _                  
        ( \_/ )       | (_(_)   __   _ __  _   _ (_)   ___    __     
       __) _ (__      `\__ \  /'__`\( '__)( ) ( )| | /'___) /'__`\                   _   _
      (__ (_) __)     ( )_) |(  ___/| |   | \_/ || |( (___ (  ___/                  ( \_/ )
         ) _ (        `\____)`\____)(_)   `\___/'(_)`\____)`\____)     _   _       __) _ (__
        (_/ \_)                                                _   _  ( \_/ )  _  (__ (_) __)         
      _   _   _               _                               ( \_/ )__) _ (__( \_/ )) _ (      
     ( ) ( ) ( )   _    _ __ ( )/')    __   _ __   ___       __) _ ((__ (_) __)) _ ((_/ \_)       
     | | | | | | /'_`\ ( '__)| , <   /'__`\( '__)/',__)     (__ (_) __)) _ ((__ (_) __)        
     | (_/ \_) |( (_) )| |   | |\`\ (  ___/| |   \__, \        ) _ (  (_/ \_)  ) _ (           
     `\___x___/'`\___/'(_)   (_) (_)`\____)(_)   (____/       (_/ \_)         (_/ \_)           

A simple implementation of off-line content cache based on service workers,

Demo   Getting Started   Submit Issue

Getting Started

A great introduction to Service Workers can be found in the References sections.

There are three events that need to be handled,

• Install,
• Activate, and
• Fetch.

The install event is fired once, activate after instal and every time a pgage from the registered domain is loaded (but not between pages from the same domain), and fetch, every time a page is requested.

                        **WORK IN PROGRESS**

References

Article, Offline content with service workers.

The Service Worker, The offline cookbook.