RE: Determine Enable/Disable state of WebExtn Installed via Registry
geoffreydebelie at zoho.com
Mon Oct 16 10:55:12 UTC 2017
This info can be found in the profiles.ini file which is located at C:\Users\username\AppData\Roaming\Mozilla\Firefox on Windows.
---- On ma, 16 okt 2017 10:07:54 +0200 Sandeep Singh <sandees at adobe.com> wrote ----
Thanks for reverting back on this. When the user has multiple FF profiles and is running one of them, and with profiles names being random alpha-numeric-special characters, is there a pivot that I can use to fetch each profile name. It is only when the directory/folder name is available to me that I can go ahead and use the extension.json under that to fetch further details about the state of the extension.
From: Dev-addons [mailto:dev-addons-bounces at mozilla.org] On Behalf Of Jefferson Scher
Sent: 16 October 2017 05:01
To: dev-addons at mozilla.org
Cc: Sachin Soni <ssoni at adobe.com>; Joydeep Majumder <jmajumda at adobe.com>
Subject: Re: Determine Enable/Disable state of WebExtn Installed via Registry
The profile.ini file uses Default=1 to point to the current default profile. However, you are correct that the user may be running a non-default profile. And the user may be using more than one profile at a time using the -no-remote startup switch.
Generally speaking, any profile in use will contain a parent.lock file. This file should not exist in other profiles in which Firefox shut down correctly. It might exist in profiles where Firefox crashed.
Is there any foolproof indicator? I'm not sure.
The extensions data moved to extensions.json. It contains an addons array of individual extension objects. You can iterate over the array looking for id=(your extension id) and then checking the properties visible=true and active=false. Query whether you want to check for userDisabled = false, indicating the user disabled it themselves which might indicate you shouldn't nag them to enable it?
Dev-addons mailing list
Dev-addons at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev-addons