While How to approach answers as software is updated deals with this kind of topics, its first answer states "It is extremely unusual for features to be removed in new version. This shouldn't be a big concern.", which clearly does not apply to Firefox's update.

So, specifically for Firefox addon recommendation questions, should we:

  • Create new questions for Firefox 57+?
  • Keep using the existing questions?
  • The premise above is inaccurate. Firefox 57 breaks some add-ons, and allows many new ones to work that would not before. For factual information, see arewewebextensionsyet.com – RockPaperLizard Nov 27 '17 at 3:53
  • @RockPaperLizard: 70% of my addons do not work anymore. None of my addons have been made "to work that would not before". – Nicolas Raoul Nov 27 '17 at 4:38
  • In statistics, that's what we call an n of 1. A sample size of 1 is not useful... except for arriving at erroneous conclusions. ;) – RockPaperLizard Nov 27 '17 at 4:46
  • BTW, my statement "allows many new ones to work that would not before" is a reference to the hundreds of Chrome extensions that have already been ported to Firefox, which was only feasible once WebExtensions was supported. – RockPaperLizard Nov 27 '17 at 4:49

As with other software where multiple versions are in active use, I don't see we'll need a special handling here. IMHO there are different groups of folks around in this context:

  • those who upgraded to FF57 and never used any addons are not affected.
  • those who upgraded to FF57 unaware and now suddenly find many of their addons broken will ask for "alternatives to X" anyway.
  • those who, aware of the changes, did NOT upgrade, or switched to a fork like Pale Moon (remaining in the "old world" of XUL/XPCom without WE support) or Firefox ESR (currently at v52 feature-wise) will find those existing answers still useful
  • those having switched to Waterfox or Basilisk (compatible with both worlds, XUL/XPCom as well as WE) will find both types of answers helpful
  • those who switched to an entirely different browser altogether (Vivaldi, Otter-Browser, qutebrowser) are not affected anyway either way

The only thing we should avoid is closing new questions clearly targeted at FF57+ as duplicates to those targeting older versions.

(Note that all alternative browsers/forks I've mentioned are cross-platform, so most Firefox users are covered)

  • LOL, you missed an entire category: "those who, aware of the changes, planned ahead and upgraded to FF57". – RockPaperLizard Nov 27 '17 at 3:58
  • @RockPaperLizard Incidentally missed, as they are not affected – and covered by the last paragraph concerning "no-dupes". – Izzy Nov 27 '17 at 7:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .