We rebuild the _recentlyUsedTabs too often from scratch. This is because we depend on the SSWindowStateReady event which fires on various occasions that aren't of interest for our purposes. I'm not even sure what exactly those occasions are. E.g. loading a page from about:newtab seems to do this. We only want to rebuild _recentlyUsedTabs when a whole window has been restored. It looks like there's currently no event specifically for this, only an nsIObserver notification.

This implements SSWindowRestored (event name inspired by SSTabRestored).

(In reply to Dão Gottwald [:dao] from comment #0) > We rebuild the _recentlyUsedTabs too often from scratch. This is because we > depend on the SSWindowStateReady event which fires on various occasions that > aren't of interest for our purposes. I'm not even sure what exactly those > occasions are. E.g. loading a page from about:newtab seems to do this. Huh? Quel oddness. Can you file a bug about that? I'll need to look at that someday...

Comment on attachment 8777770 [details] [diff] [review] patch Review of attachment 8777770 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/components/sessionstore/SessionStore.jsm @@ +3072,5 @@ > TelemetryStopwatch.finish("FX_SESSION_RESTORE_RESTORE_WINDOW_MS"); > > this._setWindowStateReady(aWindow); > > + this._sendWindowRestoredNotification(aWindow); Why not `this._sendWindowStateEvent(aWindow, "Restored");`?

Because Restored isn't one of the window states... it's either Busy or Ready. The event name should be SSWindowRestored, not SSWindowStateRestored.

(In reply to Mike de Boer [:mikedeboer] from comment #2) > (In reply to Dão Gottwald [:dao] from comment #0) > > We rebuild the _recentlyUsedTabs too often from scratch. This is because we > > depend on the SSWindowStateReady event which fires on various occasions that > > aren't of interest for our purposes. I'm not even sure what exactly those > > occasions are. E.g. loading a page from about:newtab seems to do this. > > Huh? Quel oddness. Can you file a bug about that? I'll need to look at that > someday... Well, I don't know that it's a bug...

Comment on attachment 8777770 [details] [diff] [review] patch Review of attachment 8777770 [details] [diff] [review]: ----------------------------------------------------------------- OK, convinced by comment 4. :)

Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/fx-team/rev/bbca4bc3ccd8 Implement SSWindowRestored event and use it instead of SSWindowStateReady for the Ctrl+Tab panel. r=mdeboer

We should put SSWindowRestored on devmo since the other sessionstore events are there too.