11
Comments
  • 2
    Why the fuck it requires an update?
  • 3
    @irene If I guess, the verification mechanism for Add-ons has been changed (and not just disabled), e.g. an Add-on with an expired certificate are still valid if they have been signed by the time the certificate was valid. I don't know the exact things that changed.
  • 1
    Well, this is junk xD I've seen an extension to this update's job yesterday..

    Things always get resolved after it blows up, god dangit xD
  • 1
    Oh really fucking great. And I thought it was a new "feature" of Firefox, so in frustration I removed all the "unsupported" add-ons. FML.
  • 2
    I've got a Tor browser that no longer supports NoScript due to this bug
Your Job Suck?
Get a Better Job
Add Comment