I have a button on my toolbar which restarts the browser. It uses this code: var appStartup = Components.interfaces.nsIAppStartup; Components.classes["@mozilla.org/toolkit/app-startup;1"] .getService(appStartup).quit(appStartup.eRestart | appStartup.eAttemptQuit); But since some time I notice that it doesn't restart the browser properly. It doesn't (always) read new extension info. And in Windows 7 the browser doesn't reopen in a focused state anymore (the titlebar shows inactive) and the gadgets on my desktop are displayed on top of the Firefox' sidebar. And once in about two times new info in localstore.rdf (like a newly opened sidebar) is ignored. So I'd like to know if this is a Firefox problem (a symptom of an underlying bug) or a problem in the code.
Any more details about what is failing and any regression range? The code you have basically just launches a new copy of Firefox so I'm not sure how it could be behaving any differently to a normal startup.
Component: Shell Integration → Startup and Profile System
Product: Firefox → Toolkit
QA Contact: shell.integration → startup
Don't know if it matters but I always run firefox copies from my desktop with this code: set MOZ_NO_REMOTE=1 start C:\...\...\...\firefox\firefox\firefox.exe -Profile "profile/" I'll try to find additional information.
No, there is not much further information. Didn't find a regression range either. The problems stems from before 1 Jan 2008 in any case. STR: - Open Firefox, preferably with some bookmarks, history and extensions, - Open a sidebar (ctrl+h) - Paste the code in the error console Result1: it starts up with closed sidebar Result2: a possibly open explorer window is displayed on top of the Firefox window (Firefox window has not fully focus)
Is all this only present in Windows 7?
Also on Windows XP.
Just confirming with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090202 Shiretoko/3.1b3pre I noticed that if you open a sidebar, exit, reopen, and then use the code in the error console then the sidebar opens... sounds like the state isn't saved when using restart.
You need to log in before you can comment on or make changes to this bug.