New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yellow or red alert for 'Legacy' #11108
Comments
Also, in Firefox 56.0.2, about:addons → "Extensions", the legacy extensions installed have a yellow "LEGACY" warning. Clicking on that label takes them to https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u&utm_source=inproduct that includes this bolded text:
Unfortunately, following the link to AMO from that page and then searching for an extension winds up with extension description pages that give no clue whether or not those extensions are "Compatible with Firefox 57+", which will lead to further user frustration, especially if they install a new extension to replace their old LEGACY extension and then find out 10 days later that extension will likewise cease to operate. |
Thanks @Mark12547: I have marked the knowledge base article as confusing, with reference to bug 1414626. Also I'll ping someone on the SUMO side of things. |
I'm marking this as p1 and I'll raise the question with our product people to determine if we can mirror the legacy labelling in Firefox rather than follow the same labelling used on the old AMO frontend or vice versa. |
Say we want to show a "not compatible with FF 57+" badge, we would need an icon for that (we only have an icon for "compatible with FF 57+" but not the opposite). Only web extension add-ons are compatible with FF 57+ or is there something else? |
Thought-provoking, thanks. It's precise, but maybe visually too wide for some purposes. Reading this alongside chat in IRC, first a bunch of 56.0.2 screenshots then I'll add a link to a very brief screen recording. tl;dr toying with the idea of an icon, with some yellow, to imply that something will stop working (I do already have in mind an icon, but (for myself) I need to post this, step away from the computer to the kitchen for a few minutes then come back to get some perspective) … |
For the record @willdurand here's a copy of the icon [1] - the copy as provided by @devaneymoz is "Not compatible with Firefox Quantum" |
Thanks! Exported lazily to PNG (not for reuse): Consider the possibility/likelihood that this will be confused with other meanings of the red no entry icon. In particular, the fifth screenshot above (the first in German) where I point at a red no entry icon for a greyed-out extension that bears the green badge of compatibility with Firefox 57+. Yep, I'm focusing on the visuals without paying attention to the words … |
Extensions for Firefox: a new-look scroll through two pages of 'Stop…' -named extensions – a 56 recording. Those two pages: |
|
(I changed my mind about yellow when I saw contexts – another, more significant, adjacent use of yellow. Red is fine.) |
Verified this on AMO-dev FF56(Win 7). |
For users of 56.x – and until mid 2018, users of ESR 52.x:
Precedents
Established use of a yellow rectangle for LEGACY at
about:addons
within the browser.The subtle new look yellow alert alongside Restart required at, for example, https://addons.mozilla.org/addon/quick-locale-switcher-2/
Thoughts
The requirement for Legacy extensions to be clearly identifiable as such probably arises primarily from the new look disappearance of clear identification (green badge) wherever an extension will be compatible with Firefox 57+
As there's space for the subtle yellow ⟲ for the relatively rare extensions that will require a restart of Firefox, there must be space for an unmistakable yellow alert for the relatively commonplace extensions that will be unusable with Firefox 57 and greater (all of which will, I guess, disappear from AMO sometime in Q4 2018).
It's highly desirable to have the distinction at a time of increased likelihood of people 'shopping' for extensions ahead of the mid-November release of 57.
Urgency
If you can (please):
– TIA.
Related
https://www.reddit.com/r/firefox/comments/7adng2/did_the_addon_page_change/dp9833c/ (9 points, recently up from 7):
https://www.reddit.com/r/firefox/comments/7adng2/did_the_addon_page_change/dp95kcl/ (17 points, rising):
The text was updated successfully, but these errors were encountered: