#What is mozilla firefox external link manual
#What is mozilla firefox external link code

> in FF yet leaving the application running. > that, contrary to other OS X browsers, it is not possible to close all windows This 'extra window' is annoying, and it is also a fact When an application does something as unexpected as that, many people stop trusting it per se. This must somehow be related to this bug, but I have no technical background to back me up, though. This is a serious drawback when you scroll through active windows in OS X. This 'extra window' is annoying, and it is also a fact that, contrary to other OS X browsers, it is not possible to close all windows in FF yet leaving the application running. > switching to Safari until this problem has been resolved. > however, I'm beginning this speculate that more and more Mac-users are > (or sincerely hope) that the great FF-crew is working on a permanent solution. > I too is very disappointed that this issue has not yet been resolved. > constantly is NOT a 'fix' for this issue. > Not that I want to start a huge discussion about this, but leaving FF running Because I hate open an email or a RSS from mail and two stupid I love FF but more day I pass with this bug, I want go with > have this problem, but I'm really hates this bug and I can imagine that is not > C'mon after two months you just tell that is don't fix and a method for don't

#What is mozilla firefox external link code

I think it would be good to find the bug in the command line code rather than plug in the old code to solve the problem.

#What is mozilla firefox external link manual

We could add back all the manual code for finding a window and properly opening the URL in response to the apple event but we'd essentially be duplicating the command line code, which shouldn't be necessary. I don't know why this would fail early on and I need to work on other stuff today so I'm documenting my debugging progress here. Return outDOMWindow ? NS_OK : NS_ERROR_FAILURE OutDOMWindow = do_GetInterface(docShell) InWindow->GetDocShell(getter_AddRefs(docShell)) GetDOMWindow(nsIXULWindow* inWindow, nsCOMPtr& outDOMWindow) That function, near the top of nsWindowMediator.cpp looks like this: NsWindowMediator::GetMostRecentWindow does find data (nsWindowInfo) for a most recent window, but it fails when calling GetDOMWindow with 'info->mWindow'. The problem is that the window mediator returns NULL. That calls getMostRecentWindow on nsIWindowMediator. This calls getMostRecentBrowserWindow, which calls getMostRecentBrowserWindow in nsBrowserGlue.js. I traced the failure to handURIToExistingBrowser, which is a js function in nsBrowserContentHandler.js. This should work, and it does after app startup. In the new code, we use nsICommandLineRunner and have it run with a '-url' argument. In the old apple event handling code, for kAEGetURL, we manually looked up a window by enumerating by z order via nsIWindowMediator.