On Oct 25, 2013, at 12:34 PM, Tim Taubert <ttaub...@mozilla.com> wrote: > Private tabs will be automatically excluded when bug 899276 has landed. > I don't know off-hand if setting a tab to private works even if the tab > has been around for some time but I think that might be possible.
I guess this is implied by what you said, but just to be sure: if a window contains just one private tab, the whole window won't be restored (i.e. it won't just open an empty window with no tabs in it)? >> Why are you getting rid of the nsISupportsString in >> sessionstore-state-write? Is there some urgency to doing this? > > There is no "urgency" but we're currently in the process of rebuilding > big parts of SessionStore to make it perform better. Giving add-ons that > much access to data makes it really hard to implement any kind of caching. Fair enough. It would definitely be much better to have controlled access via the API. >> Can't you fix https://bugzilla.mozilla.org/show_bug.cgi?id=930713 before you >> remove it? This seems like a pretty big lack in the current session saver >> API and something that should be straightforward to implement. > > I understand that this feature seems important to you but I disagree > that is a "big lack" in the current API. This is the first time I hear > of a requirement like that. Also fair enough. I can't speak to the overall importance of this. It does seem like an obvious bug to me that if I call window.close() any time after quit-application-requested, the window just opens anyway next time I start Firefox. > Could you maybe describe what you are actually trying to achieve and > why? Is there any add-on code we could take a look at? Maybe we can > together find a different and better solution to your problem. The simple answer is that I'm opening a popup and I want to close it when the browser quits since the contents of the popup are specific to that particular session. The more complex answer is that our framework lets people run Chrome extensions in Firefox, so I want to be able to do what Chrome does in all circumstances. In Chrome if you close a window during browser exit, it stays closed. Anyway, if there's *some* way to do this then I'm not going to complain. I'm willing to descend to arbitrary levels of hackery if there's no other way. :-) But I'd be bummed if you get rid of the nsISupports in sessionsaver-state-write without there being any other way to work around this bug. Matt _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
