This is a spin-off from https://adblockplus.org/blog/why-app-global-extensions-are-essentially-broken - it seems that Fedora will currently install extensions globally but not mark them as appManaged. Because of that the extensions will get updates via addons.mozilla.org. If the user installs such an update it will be installed in his profile (https://bugzilla.mozilla.org/show_bug.cgi?id=300967) and mask the globally installed extension. So from this point on updates to the RPM will have no effect. Fedora *could* insert <em:appManaged>true</em:appManaged> into the install.rdf file of extensions it installs. This will disable independent updates and make the extension rely solely on RPM updates. The advantage will be a much better user experience. The disadvantage: if the extension RPMs are not kept up-to-date users will get very unhappy. And as I see it right now the RPM for Adblock Plus is currently three releases behind (only Adblock Plus 1.1.3 is available which has been released in January - versions 1.2, 1.2.1 and 1.2.2 have been released since then).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.