Seems to me there are advantages to the "more complicated" version anyway.
Whilst it is reasonable to load the contents of the window they are likely to use first, I'm not sure it follows that you can avoid displaying the other windows until the first is finished loading. I imagine users could be unhappy if it takes a significant amount of time before some of their windows even appear. The thought process could go "where has my other window gone?! Oh no, did session restore not save it?!... Oh wait, there it is. phew." Perhaps the other windows could be created and displayed with a "Loading contents, please wait." message, that way, if we have a really slow and complicated session to restore, the user isn't left lacking any clue as to whether they are getting all their windows back. Of course, this assumes creating and displaying the windows isn't the costly part. On Monday, July 7, 2014 11:43:50 AM UTC+1, David Rajchenbach-Teller wrote: > Now, you are right, we can probably do as follows: > > 1. Read sessionstore.js; > > 2. Open first window; > > 3. For each window in sessionstore.js, in the order in which the windows > > have been opened initially, trigger window opening (hidden); > > 4. Once we have opened the window that should appear first, make it > > visible, restore its contents; > > 5. Asynchronously, once that window is restored and the second window > > has been opened, make it visible and restore its contents; > > 6. etc. > > > > A bit more complicated, but it should provide almost the same result. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
