If an add-on doesn't meet the requirements to be loaded as per: https://wiki.mozilla.org/Add-ons/Firefox57, then we'll want to show a reasonable warning to the user. Currently if there's a probably with signing for example you'll get a dialog that looks like the attached. We should show a nice clear message to the user as well something like "This add-on is not compatible with this version of Firefox". But I'm going to leave the actual text up to Marcus and Scott to figure out.
Summary: Show an appropriate message when an add-on is legacy technology → Show an appropriate message when an add-on is legacy technology and you attempt to install it
need this string so we can land it ASAP :) - need info markus and scott. nightly defaults true, beta defaults false. may be able to reuse text from related bug 1352204
Priority: -- → P2
I like the gist of Andy's recommended text, but I made some minor edits: This add-on is not compatible with the current version of Firefox.
Created attachment 8857916 [details] Extension-Incompatible-Warning.PNG We already have a warning for extensions that are not compatible with a certain version. We should keep using that instead of introducing another warning.
This bugs has stalled... Its not yet urgent but lets get it nailed down. Scott, see comment 4. If you want to re-use the existing message that's easy enough to do, but it sounds like Markus/UX want to distinguish the case of legacy extensions more clearly...
Assignee: nobody → aswan
I'm not seeing where Markus/UX wants to "distinguish the case of legacy extensions more clearly"? But I'm okay with Markus' suggestion to keep the language consistent in the product, so if they are to mimic each other, it would read: [Name of Add-on] could not be installed because it is not compatible with Firefox [version].
Oh whoops, you're right, I misread comment 4.
If we're sticking with the current "not compatible" error message then there isn't anything to do here.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.