Closed Bug 1120288 Opened 11 years ago Closed 11 years ago

SocialService.jsm shouldn't be using AddonManagerPrivate.notifyAddonChanged()

Categories

(Firefox Graveyard :: SocialAPI, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(firefox39 fixed)

RESOLVED FIXED
Firefox 39
Tracking Status
firefox39 --- fixed

People

(Reporter: Unfocused, Assigned: mixedpuppy)

References

Details

Attachments

(1 file)

Not sure how I missed this in my driveby review of bug 755126.... SocialService.jsm inappropriately calls AddonManagerPrivate.notifyAddonChanged() when a social provider gets disabled. It shouldn't. The notifyAddonChanged() API is meant to be used when only one add-on of a given add-on type is meant to be enabled at a time - such as themes. Thankfully, the usage here is harmless, since no code is listening for addonChanged for that add-on type. But the usage is still inappropriate and should be removed (doubly so because I want to remove that API).
Did a quick test (removing that line, running browser/base/content/test/social/browser_addons.js), seems like that line can just be removed.
Assignee: nobody → mixedpuppy
Attachment #8574966 - Flags: review?(bmcbride)
Comment on attachment 8574966 [details] [diff] [review] remove unnecessary notifyAddonChanged call Review of attachment 8574966 [details] [diff] [review]: ----------------------------------------------------------------- I wish all changes were this simple.
Attachment #8574966 - Flags: review?(bmcbride) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 39
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: