Closed
Bug 622093
Opened 14 years ago
Closed 14 years ago
After restart, Fennec shows the current page, even though the start page is set to: Fennec Start or Blank Page
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: anamaria.moldovan, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8) Gecko/20100101 Firefox/4.0b8
Build Identifier: Mozilla /5.0 (Android;Linux armv7l;rv:2.0b9pre) Gecko/20101230 Firefox/4.0b9pre Fennec /4.0b4pre
After restart, Fennec shows the current page, even though the start page is set to: Fennec Start or Blank Page
Devices:
Reproducible: Always
Steps to Reproduce:
1. Slide the webpage to the left to reveal the control tab
2. Click the options (gear) icon
3. Click the preferences (slider) icon
4. On the "Start Page" row entry, select "fennec start" or "blank page"
5. Load www.google.com (Slide to the right to reveal the tab control: make sure you have only one tab in which www.google.com has loaded)
6. Restart fennec
Actual Results:
www.google.com loads on start-up, even though the start page is set to: Fennec Start or Blank Page
Expected Results:
about:home should load on start-up with www.google.com listed in the "Your tabs from last time" section.
Reporter | ||
Updated•14 years ago
|
OS: Windows 7 → Android
Hardware: x86 → ARM
Reporter | ||
Comment 1•14 years ago
|
||
Devices: Motorola Droid 2 (Android 2.2), HTC Desire (Android 2.1)
Comment 2•14 years ago
|
||
How are you restarting Fennec in step #6?
Reporter | ||
Comment 3•14 years ago
|
||
I am using the android advanced task manager.
#6. Kill Fennec (it would have been more appropriate)
Comment 4•14 years ago
|
||
(In reply to comment #3)
> I am using the android advanced task manager.
> #6. Kill Fennec (it would have been more appropriate)
Since you are killing fennec, then the session restore is working for the "crash" and things are working as designed. If you had really restarted fennec, then the start page would have been displayed.
You can disable this behavior by changing this pref:
http://mxr.mozilla.org/mobile-browser/source/app/mobile.js#120
You can tweak the timeout used to control the session restore after crash by changing this pref:
http://mxr.mozilla.org/mobile-browser/source/app/mobile.js#121
Marking INVALID.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•