Closed Bug 876944 Opened 11 years ago Closed 10 years ago
Mode .jsm needs to handle on Widget Created/on Widget Destroyed events
CustomizeMode.jsm needs to handle the cases when an API widgets is created or destroyed, via the onWidgetCreated and onWidgetDestroyed events. Note also bug 876926, which probably necessitates the need for a onWidgetDestroying event.
Not taking this for Australis:M7.
What's the impact of not handling this? Don't know how to assign a priority otherwise.
Neither case should be common. Not handling widgets being created should just be an annoyance (so, something we want to fix, but not a priority IMO). However, not handling widgets being destroyed could break the browser window - so I think that at least should be fixed before release. That could happen in any of the following instances: * add-on updated * add-on disabled/uninstalled (via another window - unlikely, but possible) * add-on blocklisted * changing add-on references while customizing (both are "customizing my browser", so I can imagine people doing this) So, I think we can be pretty minimal with the fix here and still address the main issue. And just leave everything else to a followup when we have time.
This should do. I needed a notification after the node had been added to the windows, should it have a placement already, so I added one. Feel free to nitpick naming. :-)
Attachment #820940 - Flags: review?(bmcbride)
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Attachment #820940 - Flags: review?(bmcbride) → review+
Whiteboard: [Australis:P4] → [Australis:P4][Australis:M9][fixed-in-ux]
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:P4][Australis:M9][fixed-in-ux] → [Australis:P4][Australis:M9]
Target Milestone: --- → Firefox 28
You need to log in before you can comment on or make changes to this bug.