Compromise: Develop it as a Plugin and then install it by default. That way people who don’t want the feature can easily remove it completely. That approach would likely also reduce the number of Firefox forks whose sole purpose is to remove the new features some consider bloat.
Probably handle it similarly to how Chrome handles an extension asking for new permissions. It disables the add-on and gives the user a small non-intrusive notification on the options menu. Opening the notification notified the user about the change in permissions and asks them if they want to re-enable the add-on or remove it from Chrome.
Compromise: Develop it as a Plugin and then install it by default. That way people who don’t want the feature can easily remove it completely. That approach would likely also reduce the number of Firefox forks whose sole purpose is to remove the new features some consider bloat.
That’s actually what Firefox usually did for these kind of features. They’re usually delayed as system add-ons.
Good solution, perhaps two simple options at browser install: Default / Custom. That way you don’t have to uninstall all the stuff at the end.
deleted by creator
Probably handle it similarly to how Chrome handles an extension asking for new permissions. It disables the add-on and gives the user a small non-intrusive notification on the options menu. Opening the notification notified the user about the change in permissions and asks them if they want to re-enable the add-on or remove it from Chrome.