Closed Bug 1526360 Opened 5 years ago Closed 5 years ago

CFR no longer respects the xpinstall.enabled pref

Categories

(Firefox :: New Tab Page, defect, P1)

defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox65 - wontfix
firefox66 - wontfix
firefox67 - wontfix

People

(Reporter: Felipe, Unassigned)

References

Details

(Keywords: regression)

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

+++ This bug was initially created as a clone of Bug #1494778 +++

This had already been fixed in bug 1494778, but according to bug 1525340, this regressed on 65.

Bug 1525340 is papering over this for the enterprise policy case, but there are other ways that people change that pref (autoconfig or even manually).

Is it possible to include a test to cover this? If extensions are not allowed to be installed, CFR really should not be recommending them.

See Also: → 1525340

Hello Marius, could you retest this to see if this happens or if it was just a false alarm?

Flags: needinfo?(marius.coman)

I have verified this issue with the latest Firefox Release (65.0 Build ID - 20190124174741), Firefox Beta (66.0b6 Build ID - 20190207161357), and Firefox Nightly (67.0a1) installed, on Windows 10 x64, Arch Linux and Mac 10.13.3. Now, the CFR recommendations are not displayed if the "xpinstall.enabled" pref is added in the "about:config" with the "false" value.

Flags: needinfo?(marius.coman)

Great, thanks

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.