Closed Bug 973085 Opened 12 years ago Closed 11 years ago

Do initialization in onCreate instead of onWindowFocusChanged

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1085591

People

(Reporter: bnicholson, Unassigned)

References

Details

onWindowFocusChanged isn't designed to be used for application initialization. IIRC, we use it because it happens later in startup and allows us to show an empty window more quickly; however, the docs say that it is "managed independently of activity lifecycles" and apps "should not rely on any particular order between the callbacks here and those in the other lifecycle methods" (http://developer.android.com/reference/android/app/Activity.html#onWindowFocusChanged%28boolean%29). We should simply do initialization in onCreate(): onCreate is fired exactly once, and it's the intended hook for initialization.
Blocks: 966788
I tried simply moving the initialize() call, but that did not work: https://tbpl.mozilla.org/?tree=Try&rev=7c81292ec94a
The patch bug 966788 comment 138 landed an increased wait time for Gecko:Ready - we should probably revert that back once this bug is solved.
See Also: → 1085591
Forward-duping.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.