Page 1 of 1

Extension Preferences Are Not Enumerated in about:config

Posted: Fri Jan 26, 2018 3:02 am
by therube
(Just dawns on me...)

- Extension Preferences Are Not Enumerated in about:config - in Quantum

Is that correct?
And if not, where are they, & just how is a "human" supposed to make sense of things?
Another black box, essentially hidden.

Suppose (though such things "can't" happen, I suppose), suppose, you put in an extension xyz.
And xyz goes in & modifies NoScript's whitelist, setting particular sites to Allowed...

Sure, you can look at NoScript's (what I consider) very basic "interface" (Options), & you might catch that.

But suppose it changes some other preference that is not enumerated in NoScript Options itself.
Just how is one going to find something like that?

Re: Extension Preferences Are Not Enumerated in about:config

Posted: Fri Jan 26, 2018 3:14 am
by barbaz
Don't know if this applies to every WebExtension, but the WebExtensions I wrote their data gets stored in profile/browser-extension-data/<extension-ID>/storage.js

Re: Extension Preferences Are Not Enumerated in about:config

Posted: Fri Jan 26, 2018 3:32 am
by therube
Don't know if this applies to every WebExtension
https://forums.informaction.com/viewtop ... =7&t=23961 ;-)

And yet I throw it into 3 online sqlite viewers & 2 downloaded sqlite viewers, & I'll be if I'm getting anything out of it? (I get more information running storage-sync.sqlite through strings.)


And, http://forums.mozillazine.org/viewtopic ... #p14787340.

Re: Extension Preferences Are Not Enumerated in about:config

Posted: Wed Mar 21, 2018 1:31 am
by barbaz
therube wrote:And yet I throw it into 3 online sqlite viewers & 2 downloaded sqlite viewers, & I'll be if I'm getting anything out of it?
Did you try sqlitebrowser?

Re: Extension Preferences Are Not Enumerated in about:config

Posted: Wed Mar 21, 2018 3:27 am
by GµårÐïåñ
WebExtensions do not expose their settings in the about:config anymore, they are placed inside IndexDB structure, and as such you won't see them in the browser. Using a db viewer is an option but not always reliable, and could actually end up corrupting the extension's data or even cause the browser to fail validation and dump it.

What settings are you looking for that you can't see inside the GUI?