Closed
Bug 702265
Opened 13 years ago
Closed 6 years ago
Third party add-ons are disabled by default with no interaction by user on a fresh install
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mkaply, Unassigned)
References
Details
If a user installs Firefox 8 for the first time, and a third-party add-on was installed before Firefox was installed, that add-on will be disabled with no interaction from the user. They should be asked. I encountered this by having Fiddler installed and then creating a new profile. Fiddler was disabled, and I was never asked to enable it.
Comment 1•13 years ago
|
||
This was intentional to avoid bombarding the users with choices immediately after they first install Firefox. I'm sure we could do better but I'm not exactly sure what form that would take at this point. Maybe asking on the second run or something?
Keywords: uiwanted
Comment 2•13 years ago
|
||
"Ux-control is often the nemesis of ux-interruption". You're going to answer that "Interfaces should never ask the user a question that they are not prepared to answer simply for a false sense of ux-control"; but IMHO high-handedly disabling an add-on (for whatever reason) without the user's say-so is worse, unless there is a very important reason to do so. Incompatibility with a new release is such a reason. Having been installed by a third party is much more debatable. Maybe present the about:newaddons dialog if third-party addons are found?
Keywords: ux-control
Comment 3•13 years ago
|
||
Can't we use a notification bar / doorhanger to inform the user that 3rd party add-ons have been found and need to be enabled to work? Not sure how this would interfere with our first-run notification bar.
Comment 4•12 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #1) > This was intentional to avoid bombarding the users with choices immediately > after they first install Firefox. I'm sure we could do better but I'm not > exactly sure what form that would take at this point. Maybe asking on the > second run or something? I think the current behavior is fine — if people are missing an add-on, they will go looking for it in the add-ons pane (if they actually intended to install it, that is!), and enabling it there isn't difficult.
Keywords: uiwanted,
ux-control
Updated•10 years ago
|
Comment 6•6 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Reporter | ||
Updated•6 years ago
|
Resolution: INACTIVE → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•