Closed Bug 1593508 Opened 5 years ago Closed 5 years ago

Add-ons broken in v70 and 70.0.1

Categories

(Core :: Storage: IndexedDB, defect, P2)

70 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1335919

People

(Reporter: my.mail.001, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Autoupdate from v69 to v70 and v70.0.1
I even tried the workaround "Change the dom.storage.next_gen preference to false" but it did not help (including restarting).
Clean profile didnt change anything.

Actual results:

The following add-on stopped working:

  • NoScript
  • uBlock origin
  • Smart Referer
  • First Party Isolation
    All those add-on ons do show an icon in the title bar which you can use to see their effects and configure them.
    UBlock Origin and noscript only show nonworking popups. See attached screenshot.
    NoScript seems to work sometimes and sometimes not.
    Smart Referer and First party isolation dont turn on after licking on them as they should.
    Firefox storage test shos some bugs, see attached screenshot

Expected results:

The add-ons should continue to work as they did in v69.

Component: Untriaged → DOM: Web Storage
Flags: needinfo?(bugmail)
Product: Firefox → Core

Hm, so this is likely coming from various permission checks[1] and it's breaking WebExtensions because the preference "extensions.webextensions.ExtensionStorageIDB.enabled" is enabled which causes WebExtensions to use IndexedDB for storing their configuration. Alternately,

Questions:

  • Is the preference dom.indexedDB.enabled somehow set to false for your installation? (Check using "about:config", https://support.mozilla.org/en-US/kb/about-config-editor-firefox)
  • Do you have privatebrowsing mode set to be always on? I wouldn't think so given that cache API is working, but I want to check.
  • Have you made any other default privacy / permission settings changes? (Note that the extensions should be benefiting from a special check that grants such privileges to extensions, so what firefox-storage-test reports isn't exactly the same as what's happening for your extensions, but it does seem likely.)
  • Are you using anti-virus software other than Windows Defender?
  • Is your profile stored on a network drive somehow? (Roaming profiles should store things locally, but there can be other configurations that are possibe?)

1: https://searchfox.org/mozilla-central/search?q=NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR&redirect=false

Component: DOM: Web Storage → DOM: IndexedDB
Flags: needinfo?(bugmail) → needinfo?(forumuser001)
Priority: -- → P2

Questions:

Yes, it is set to false.

  • Do you have privatebrowsing mode set to be always on? I wouldn't think so given that cache API is working, but I want to check.

No, I rarely use that.

  • Have you made any other default privacy / permission settings changes? (Note that the extensions should be benefiting from a special check that grants such privileges to extensions, so what firefox-storage-test reports isn't exactly the same as what's happening for your extensions, but it does seem likely.)

I did not change anything recently, when it broke.
In settings Tracking protection is set to user defined with everything (all 4 checkmarks) activated.

  • Are you using anti-virus software other than Windows Defender?

Kaspersky

  • Is your profile stored on a network drive somehow? (Roaming profiles should store things locally, but there can be other configurations that are possibe?)

No, all local.

Flags: needinfo?(forumuser001)

(In reply to forumuser001 from comment #2)

Questions:

Yes, it is set to false.

Ah, yeah, it needs to be set back to true. I'll put up a fix for bug 1488583 now.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE

Thanks for all the help! It now seems to work again. :-)

3 questions, if you spare the time:

  1. Should I reset "dom.storage.next_gen" to true now again also?
    I changed it to false after reading this: https://www.bleepingcomputer.com/news/software/mozilla-provides-workaround-for-firefox-70-not-loading-sites/ as I was speculating it would help.

  2. Any idea what caused the change to "dom.indexedDB.enabled"? I am pretty sure I did not manually change something in about:config recently.

  3. Is there a foolproof method for noobs like me to reset the whole lot of settings under about:config to "default" without creating a blank new profile from scratch?

(In reply to forumuser001 from comment #4)

  1. Should I reset "dom.storage.next_gen" to true now again also?
    I changed it to false after reading this: https://www.bleepingcomputer.com/news/software/mozilla-provides-workaround-for-firefox-70-not-loading-sites/ as I was speculating it would help.

The default on 70 is once again false, so it's fine to leave it.

  1. Any idea what caused the change to "dom.indexedDB.enabled"? I am pretty sure I did not manually change something in about:config recently.

Maybe you installed the extension at https://github.com/ChrisAntaki/disable-indexeddb or used https://github.com/pyllyukko/user.js or https://github.com/ghacksuserjs/ghacks-user.js, the latter two of which seemed to at least be thinking about setting the pref to false?

  1. Is there a foolproof method for noobs like me to reset the whole lot of settings under about:config to "default" without creating a blank new profile from scratch?

https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings but do read the disclaimers because it somewhat assumes your extensions are part of the problem you're trying to fix.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: