Don't downgrade Firefox 63 - gHacks Tech News

Don't downgrade Firefox 63

Mozilla plans to change the backend for the storage.local API to indexedDB from JSON to improve performance in Firefox 63. The migration happens in the background and Firefox users who run Firefox 63 should not notice any issues afterward.

Problems may arise however if users downgrade Firefox to an earlier version or switch to a channel that is not yet at Firefox 63 or newer.

The change will land in Firefox Nightly first and if users load the Beta or Stable version of Firefox with the Nightly profile, they may run into data regression issues with extensions installed in the browser.

Mozilla revealed the change on the organization's Add-ons blog that it uses to inform developers of extensions for Firefox about upcoming changes and new features.

If your users switch between Firefox channels using the same profile during this time, they may experience data regression in the extensions they have previously installed.

Mozilla recommends that users don't downgrade from Firefox 63 in any form (be it by installing an older version and running it, or running an older version that is installed already using the same profile).

How to find out if the data has been migrated

firefox 63 downgrade

You can do the following to find out if the storage API has been migrated already to the new storage format:

  1. Load about:config?filter=extensions.webextensions.ExtensionStorageIDB.enabled in the address bar of the browser.
  2. Check the value of the preference.
    • True means that the data has been migrated.
    • False that Firefox uses the old format.
  3. Search for extensions.webextensions.ExtensionStorageIDB.migrated.
    1. If the Extension ID is set to true, the extension storage has been migrated.

What you can do to re-migrate the data

extensions migrated

Mozilla published instructions on re-migrating the extension data should it not be there after the migration. Note that it requires quite a few steps including removing the extension from Firefox and reinstalling it.

  1. Open about:debugging and write down the extension ID (or remember it).
  2. Open the profile folder of Firefox by loading about:profile and there the open folder option.
  3. Open the folder browser-extension-data.
  4. Open the Extension ID folder.
  5. Uninstall the extension.
  6. Copy the file storage.js.migrated which you find in the Extensions ID folder to a new file and name it storage.js.
  7. Open the browser console by selecting Menu > Web Developer > Browser Console or by using the shortcut Ctrl-Shift-J.
  8. Install the extension again.
  9. The browser console should display a migration message. Wait for this to happen.

Closing Words

If you need to run different Firefox channels, use different profiles (and you can even run the profiles simultaneously). You can copy profile data from one profile to the other to create copies if you want to work with the same data set.

Summary
Don't downgrade Firefox 63
Article Name
Don't downgrade Firefox 63
Description
Mozilla plans to change the backend for the storage.local API to indexedDB from JSON to improve performance in Firefox 63.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:


Previous Post: «
Next Post: »

Comments

  1. Anonymous said on August 6, 2018 at 7:55 pm
    Reply

    There’s something odd going on with mozilla.org lately. I can’t open the “mobile” folders of https://releases.mozilla.org/ , https://archive.mozilla.org/ and https://ftp.mozilla.org/. For example, I can open https://releases.mozilla.org/pub/ as well as https://releases.mozilla.org/pub/mobile/releases/ , but https://releases.mozilla.org/pub/mobile/ throws a 404 Not Found (or occasionlly a 504 Error).

    Is this only me?

    1. Richard Allen said on August 6, 2018 at 9:57 pm
      Reply

      Same here.

      I’ve always used “https://www.apkmirror.com/” for browser updates on Android. If I didn’t want to wait. And I wouldn’t mention them if I didn’t feel they were trustworthy. Just saying.

  2. Satya Nadella Quote Generator said on August 6, 2018 at 7:59 pm
    Reply

    Downgrade is for pussies

    1. Richard Allen said on August 6, 2018 at 9:58 pm
      Reply

      LMAO

    2. TrackingCookieMonster said on August 8, 2018 at 11:40 am
      Reply

      Keeping data in your browser is for pussies. Clean on exit gang.

  3. Richard Allen said on August 6, 2018 at 10:02 pm
    Reply

    Thanks Martin, I wasn’t aware of that. I’ve been slacking about going to mozillaZine lately and haven’t checked the twitter feed lately. Shame on me.

  4. AAA said on August 6, 2018 at 10:56 pm
    Reply

    Mozilla is becoming more like Internet Explorer :(
    …today; I tried 32bit, 64bit, custom installation, automatic — but none could get sharp crispy Netflix quality that I could get via Edge.
    What did the fox say? 🙄

    1. ZeoMal said on August 7, 2018 at 7:36 am
      Reply

      If you look it up, that’s got nothing to do with Mozilla per se, as Netflix supports the highest quality (https://www.reddit.com/r/firefox/comments/7e3xtd/does_ff_quantum_support_1080p_netflixhdr_4k_amazon/), only in Microsoft’s own browser.

    2. Jonh said on August 7, 2018 at 8:32 am
      Reply

      Same here sometimes. However one day I was browsing with Edge and one page didn’t work properly (weird issue considering its UA like Chrome), so I decided to open it with Firefox latest and it worked fantastic (showing tick boxes and web dialogs that didn’t appear with Edge). I remember one site that only worked for me with IE11, some months ago, so surprisingly.

    3. Richard Allen said on August 7, 2018 at 7:08 pm
      Reply

      I recently did a clean install of Win7 on my 9 year old laptop and gave it to my sister because she only has a work computer and often works from home.

      She just now told me Netflix is working fine for her and she’s using FF v61 x64. Laptop has a dual core processor, a GT 230M graphics card, 4GB of RAM with an inexpensive ADATA SSD hooked up to a 100+ Mbps connection. Nothing special.

      I think she was a little put out that I asked her to look. LoL. She normally watches Netflix on her ridiculously large Smart TV. Definitely a spoiled girl!

  5. jan said on August 7, 2018 at 11:03 am
    Reply

    Yes, one more thing to know and how to fix it in the postgraduate PhD program for advanced users. But the FF people do not want to know how close they are to the point of meltdown.

  6. Anonymous said on August 7, 2018 at 3:16 pm
    Reply

    What does that means? They’ll replace .json with sqlite DBs?

    1. Martin Brinkmann said on August 7, 2018 at 4:35 pm
      Reply

      At least in this case, yes.

  7. Robert Ab said on August 7, 2018 at 6:38 pm
    Reply

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.