question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

yellow or red alert for 'Legacy'

See original GitHub issue

For users of 56.x – and until mid 2018, users of ESR 52.x:

  • there should be an upfront indication wherever an extension is legacy.

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):

  • Monday 2017-11-06 for a Tuesday freeze and push on Thursday 2017-11-09

– TIA.

Related

https://www.reddit.com/r/firefox/comments/7adng2/did_the_addon_page_change/dp9833c/ (9 points, recently up from 7):

How can I see if an addon is FF 57+ ready now?

https://www.reddit.com/r/firefox/comments/7adng2/did_the_addon_page_change/dp95kcl/ (17 points, rising):

… can’t tell anymore … 57 or not.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:2
  • Comments:11 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
ValentinaPCcommented, Nov 7, 2017

Verified this on AMO-dev FF56(Win 7). The new label was added. As the issue #3814 was logged separately, I think we can mark this as verified-fixed. Postfix screenshot: 2017-11-07_1229 2017-11-07_1231

1reaction
muffinresearchcommented, Nov 6, 2017

For the record @willdurand here’s a copy of the icon [1] - the copy as provided by @devaneymoz is “Not compatible with Firefox Quantum”

[1] not-compatible-min.svg.zip

Read more comments on GitHub >

github_iconTop Results From Across the Web

Subaru Legacy Light Guide | Freehold Subaru NJ
Common yellow lights you may encounter in your legacy include: ... A more serious situation is when you see a red warning light...
Read more >
Subaru Warning Lights | What Do They Mean?
See the different warning lights in Subaru models and what you can do to help diagnose the cause. ... High beam assist indicator...
Read more >
Subaru Dashboard Warning & Indicator Light Guide
Find out what the warning light appearing on your Subaru's dashboard means with help from Koeppel ... High beam assist indicator (yellow) (if...
Read more >
Warning Light References - Vehicle Maintenance
SRS airbag system warning light​​ Indicates that the Supplemental Restraint System has detected a malfunction and the airbags and/or seatbelt pre-tensioners ...
Read more >
Subaru Service Lights & Dashboard Symbols
The Red Oil Can. This light indicates an oiling issue and is one of the most critical of all Subaru warning lights. If...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found