294127 - When Camino is launched with a document, init order is incorrect

Status: RESOLVED FIXED

(Camino Graveyard :: General, defect, P2)

Description

[Simon Fraser [no longer active]]

If you launch camino by dragging a file onto its icon, then you'll see some
console spewage in debug builds which indicates that we're trying to load stuff
before we've fully initted gecko:

###!!! ASSERTION: EnableGlobalHistory() failed: 'NS_SUCCEEDED(rv)', file
../../../../../mozilla/embedding/browser/webBrowser/nsWebBrowser.cpp, line 1208

WARNING: NS_ENSURE_TRUE(mRequest) failed, file
../../../../../../mozilla/netwerk/protocol/file/src/nsFileChannel.cpp, line 172

WARNING: NS_ENSURE_TRUE(mRequest) failed, file
../../../../../../mozilla/netwerk/protocol/file/src/nsFileChannel.cpp, line 172

WARNING: NS_ENSURE_TRUE(mRequest) failed, file
../../../../../../mozilla/netwerk/protocol/file/src/nsFileChannel.cpp, line 172

What's happening is that we handle the open document stuff before
-appDidFinishLaunching is called, so we haven't yet registered the app
components and done other setup.

The impact of this is that history is broken for that first browser view.

Comment 1

[Simon Fraser [no longer active]]

*** Bug 300616 has been marked as a duplicate of this bug. ***

Comment 2

[Simon Fraser [no longer active]]

Attachment: Patch

This patch makes sure that we init gecko before doing stuff like handling
GetURL	or application:open: events on launch, since these are called before
-applicationDidFinishLaunching

Comment 3

[Simon Fraser [no longer active]]

Fixed.