These options make it much easier to remove a cache if it is required for testing a code update. You can also click on one of the individual items stored in the cache, then Right/ Ctrl click on it to get options for deleting just that item, or every item in the cache. Right/ Ctrl clicking on one of the caches gives you two options:ĭelete All - delete all caches under this origin.ĭelete “name of cache” - delete only the highlighted cache. The Firefox DevTools Storage tab has a Cache Storage section that lists all the different Caches you have stored under each different origin. When you fill up the cache with assets, but then want to alter the behavior slightly, you previously had to manually write code to empty the cache, and then fill it again. If you are using your service worker to store your site assets in Cache Storage (using the Cache API), which is essential for creating offline apps, it can be annoying to test the cache. When pressed (and if service worker debugging is enabled), this takes you straight to the JavaScript debugger view of your service worker code, and you can use the full power of the debugger to debug it - stepping through code, etc. When your service worker is running, the Arrow button available next to the Source information (it is disabled when the service worker is stopped). Enabling this can degrade the performance of the Debugger. Important: The debugging feature is currently enabled only in Firefox Nightly via the experimental feature “Developer Tools: Service Worker debugging”. As soon as there are no more such pages still loaded, the new service worker activates. It is only activated when there are no longer any pages loaded that are still using the old service worker. If your service worker has previously been installed, but then a new version of the worker is available on refresh or page load, the new version is installed in the background, but not yet activated. This is very useful because, once registered, the service worker will not necessarily update to the new version immediately, which can make debugging a pain. On the right-hand side of the Service Workers view there is an Unregister button, which when pressed unregisters the service worker. There are a couple of other useful controls on this view, too. When the service worker is stopped, a Start button is provided to start it running, allowing you to trigger the service worker lifecycle. Stopped: The service worker is installed, but not currently running. The server worker’s status, which can be one of the following: The path to the service worker source file. That last time the service worker was updated (if the service has not been updated, this is when it was first installed). The URL that the service worker is registered on. This gives you a variety of information about your service worker: In any case, when the service worker is successfully registered, you’ll see information about it displayed in the Application > Service Workers view (along with any other service workers registered on the same domain): If this is not enough to help you figure out the problem, you could also try going to the JavaScript Debugger and stepping through your code to pinpoint exactly where it is going wrong. If you get the path wrong, for example, you’ll get an error in the Web Console giving you a hint as to what’s wrong, which depends on what exactly is wrong with the code. Turning on Firefox tests for a new configuration.

Getting Set Up To Work On The Firefox Codebase.

Firefox dev tools