{"id":8614,"date":"2019-02-15T14:04:43","date_gmt":"2019-02-15T22:04:43","guid":{"rendered":"http:\/\/blog.mozilla.org\/addons\/?p=8614"},"modified":"2019-02-15T14:05:34","modified_gmt":"2019-02-15T22:05:34","slug":"extensions-in-firefox-66","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/addons\/2019\/02\/15\/extensions-in-firefox-66\/","title":{"rendered":"Extensions in Firefox 66"},"content":{"rendered":"

Firefox 66 is currently in beta and, for extension developers, the changes to the WebExtensions API center primarily around improving performance, stability, and the development experience. A total of 30 issues<\/a> were resolved in Firefox 66, including contributions from several volunteer community members.<\/p>\n

Major Performance Improvements for Storage<\/h2>\n

I want to start by highlighting an important change that has a major, positive impact for Firefox users. Starting in release 66, extensions use IndexedDB as the backend<\/a> for local storage instead of a JSON file. This results in a significant performance improvement for many extensions, while simultaneously reducing the amount of memory that Firefox uses.<\/p>\n

This change is completely transparent to extension developers – you do not need to do anything to take advantage of this improvement. \u00a0When users upgrade to Firefox 66, the local storage JSON file is silently migrated to IndexedDB. All extensions using the storage.local() API immediately realize the benefits, especially if they store small changes to large structures, as is true for ad-blockers, the most common and popular type of extension used in Firefox.<\/p>\n

The video below, using Adblock Plus as an example, shows the significant performance improvements that extension users could see.<\/p>\n