Closed
Bug 1422434
Opened 7 years ago
Closed 7 years ago
Expose history.enabled pref
Categories
(WebExtensions :: Untriaged, enhancement)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1363860
People
(Reporter: jhirsch, Unassigned)
References
Details
Firefox Screenshots needs to be able to set cookies to allow shots to be uploaded. In some cases, like when history is disabled, no browser storage is available. Currently, Screenshots has to check the history.enabled pref to see if this is the case, and checking prefs requires Screenshots to have a bootstrapped part. It would be great to expose this pref (or the availability of browser storage) to webextensions.
Comment 1•7 years ago
|
||
If this is just about knowing whether cookies are enabled, can bug 1363860 be considered a dupe of this?
Flags: needinfo?(jhirsch)
Reporter | ||
Comment 2•7 years ago
|
||
> If this is just about knowing whether cookies are enabled, can bug 1363860 be considered a dupe of this? Yes, this bug is just about Screenshots being able to tell if cookies are enabled. This seems to be a subset of bug 1363860, so this might be duped to that one.
Flags: needinfo?(jhirsch)
Comment 3•7 years ago
|
||
(In reply to Jared Hirsch [:_6a68] [:jhirsch] from comment #2) > > If this is just about knowing whether cookies are enabled, can bug 1363860 be considered a dupe of this? > > Yes, this bug is just about Screenshots being able to tell if cookies are > enabled. This seems to be a subset of bug 1363860, so this might be duped to > that one. Once bug 1363860 lands you should be able to call browser.privacy.websites.cookieBehavior.get({}) and be returned a value that tells you the current setting, which explains which types of cookies, if any, are being accepted by the browser.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•