Closed
Bug 878491
Opened 12 years ago
Closed 12 years ago
About:home is cut off beneath title bar after OOM kill on non-about:home page
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox23+ verified, firefox24+ verified)
RESOLVED
FIXED
Firefox 24
People
(Reporter: bnicholson, Assigned: bnicholson)
References
Details
(Whiteboard: [testday-20130726])
Attachments
(1 file)
2.73 KB,
patch
|
lucasr
:
review+
|
Details | Diff | Splinter Review |
I'm still seeing bug 869411 in the latest Nightly.
STR:
1) Open Fennec and see about:home
2) Go to google.com
3) Minimize Fennec and cause it to be killed in the background (i.e., open several other apps or use oom-fennec)
4) Reopen Fennec
5) Click back to go to about:home
After doing this, the top of about:home is cut off.
Assignee | ||
Comment 1•12 years ago
|
||
Bug 869411 did fix the case where the activity is destroyed/recreated while about:home is showing, but I must have forgotten to test the case where about:home isn't visible (as in the STR above). When we leave about:home, we fully remove (not just detach) the fragment, so it is no longer managed by the FragmentManager and its state isn't saved.
Assignee | ||
Comment 2•12 years ago
|
||
Saves the about:home padding state in BrowserApp instead of the AboutHome fragment since the fragment won't save state after being removed. We'll have to end up doing this anyway with our new about:home changes since HomePager isn't a fragment.
Attachment #757056 -
Flags: review?(lucasr.at.mozilla)
Assignee | ||
Updated•12 years ago
|
Summary: About:home is (still) cut off beneath title bar → About:home is cut off beneath title bar after OOM kill on non-about:home page
Updated•12 years ago
|
Attachment #757056 -
Flags: review?(lucasr.at.mozilla) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 24
Updated•12 years ago
|
Updated•12 years ago
|
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
I can verify this is fixed in a Galaxy S2 phone with Android 4.0.3 and the latest Firefox Beta.
Whiteboard: [testday-20130726]
Updated•12 years ago
|
Comment 7•12 years ago
|
||
I am unable to reproduce the issue on Firefox Mobile 23 RC and Aurora 24.0a1 2013-07-31 on the Samsung Galaxy R (Android 2.3.4)
Updated•5 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
•