Files
tubestation/browser/components/extensions
Bob Silverberg 03a66f5cfc Bug 1366290 - Fix the ordering of tabs.onActivated and tabs.onRemoved, r=kmag
Currently tabs.onActivated (for the tab that becomes active after a tab is removed) fires before
tabs.onRemoved (for the tab that was removed). This is neither the order in which Chrome fires
these events, nor is it the order in which the internal TabSelect and TabClose happen in Firefox.
This bug fixes this so tabs.onActivated fires *after* tabs.onRemoved.

Note that this does introduce an issue in in-process mode, where window.close() will not
trigger a tabs.onRemoved event for the window, but Kris says "Meh" about that.

MozReview-Commit-ID: CrFR3jqL2u5
2017-05-31 12:01:58 -04:00
..