Closed
Bug 975357
Opened 11 years ago
Closed 11 years ago
Initialize HomeConfigInvalidator in GeckoApplication.onCreate()
Categories
(Firefox for Android Graveyard :: Awesomescreen, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 30
People
(Reporter: lucasr, Assigned: lucasr)
References
Details
Attachments
(1 file)
1.65 KB,
patch
|
Margaret
:
review+
|
Details | Diff | Splinter Review |
Instead of initialize().
Assignee | ||
Updated•11 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Comment 2•11 years ago
|
||
Comment on attachment 8379641 [details] [diff] [review]
Initialize HomeConfigInvalidator in GeckoApplication.onCreate() (r=margaret)
HomeConfigInvalidator should be bound to the application as a whole, not specifically to the main activity. initialize() is only called when BrowserApp starts but we need HomeConfigInvalidator to be around even if you restore the Fennec directly into, say, the Settings activity.
Attachment #8379641 -
Flags: review?(margaret.leibovic)
Updated•11 years ago
|
Attachment #8379641 -
Flags: review?(margaret.leibovic) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Comment 4•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
Comment 5•11 years ago
|
||
Setting P1 hub bugs to block hub v1 EPIC bug (targeting fx30 release).
Filter on epic-hub-bugs.
Blocks: 1014025
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•