Closed Bug 1298955 Opened 8 years ago Closed 7 years ago

Make it clear what add-on overrode what

Categories

(WebExtensions :: Frontend, defect, P3)

defect

Tracking

(firefox51 affected)

RESOLVED DUPLICATE of bug 1354344
Tracking Status
firefox51 --- affected

People

(Reporter: andy+bugzilla, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: triaged)

In bug 1234150 and (possibly) bug 1298950 there's the ability for add-ons to override parts of the Firefox experience, like the newtab or the home page. The problem is that its basically a "last add-on wins" kind of experience. 

There's no real information to the user telling them what add-on took control of the newtab. I think we might need some UX help here in deciding if this is worth bubbling up to the user, if its worth giving the user options about choosing an add-on that gets to override etc...

Its worth noting that this might occur for other APIs where add-ons collide with each other.
For the replacement of parts of the browser experience, Chrome has a solutions that works great as far as I can tell.
https://github.com/mozilla/addons/issues/51#issuecomment-220948578
They will inform the users on their first visit of the affected page about the change (while the change is applied so that users see the difference) and ask them to confirm. If the users does not confirm, Chrome will ask again in the next browser session. If the user confirms they will leave it as the new default. If the user declines, they will revert back to the last override of the affected page. (Previous extension or browser default, whatever the user had last.)

Additionally Chrome surfaces the change next to the setting of the affected page. (e.g. next to the settings entry to set the location of newtab.)
Priority: -- → P3
Whiteboard: triaged
Depends on: 1342584
Remarkably similar to bug 1354344, but that has more details.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.