Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Firefox updates blocking leethax.net extension?

  • 3 одговорa
  • 1 има овај проблем
  • 3 прегледа
  • Последњи одговор послао MightyMagician

more options

Hi,

I play Angry Birds Friends on Facebook, and I am a user of the leethax.net extension. A few days ago I found that the extension stopped working after a Firefox update, and nothing detailed in the update log indicated they were blocking leethax. But when I reverted to the previous version of Firefox - it worked! Why is Mozilla blocking an extension I love using?

Thanks, MM

Hi, I play Angry Birds Friends on Facebook, and I am a user of the leethax.net extension. A few days ago I found that the extension stopped working after a Firefox update, and nothing detailed in the update log indicated they were blocking leethax. But when I reverted to the previous version of Firefox - it worked! Why is Mozilla blocking an extension I love using? Thanks, MM

Сви одговори (3)

more options

hi mm, extensions are maintained by independent third-party developers - firefox doesn't block any addons unless they are a security or stability thread (but that's not the case here). if the extension stopped working after an update you'll have to get in contact with the addon's developers and ask them to make it compatible with a new version of firefox...

more options

Are there any messages about this extension in the Browser Console?

more options

Hi,

While I'm aware that the developers of leethax have released their own updates since the Firefox update, nothing detailed in the latest release would actually make the extension incompatible - it was general fixes for tabs and a minor PDF issue. In other words: Mozilla's own update should not be interfering with leethax. I've also checked the Browser Console article and found nothing that could help. At this point I can only assume that the update also had something that blocks the extension deliberately.

Thanks, MM