Closed
Bug 1144019
Opened 10 years ago
Closed 3 years ago
browser.startup.page is not working
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: david.bruchmann, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150305021524
Steps to reproduce:
I restarted my browser with plenty of open tabs.
Version 36.0.1
Actual results:
In browser.startup.page I entered usually the value 3 (by the options panel) to get all the tabs opened again. This never works anymore.
The option to display the last opened tabs still is shown in the options panel but grayed out / disabled. In about:config the value 3 is still present but without any impact.
Expected results:
1) The before opened tabs tabs should have been opened again at browser-startup.
2) The option to open before opened tabs again never should be grayed out / disabled.
Reporter | ||
Updated•10 years ago
|
Severity: normal → major
Whiteboard: Tabs are not opened at startup
Reporter | ||
Updated•10 years ago
|
Component: Untriaged → Tabbed Browser
Did you try to reset the value in about:config?
Keywords: access,
ue,
useless-UI,
ux-consistency,
ux-mode-error,
ux-trust
Whiteboard: Tabs are not opened at startup
Reporter | ||
Comment 2•10 years ago
|
||
I switched to another value and then back to 3 (by about:config)
I restarted the whole PC too - no change.
If you start FF in safe mode, does FF restore your tabs open?
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Reporter | ||
Comment 4•10 years ago
|
||
No, it doesn't change that the last opened tabs are ignored.
Comment 5•3 years ago
|
||
Marking this as Resolved > wfm since I cannot reproduce the issue using the latest Fx versions, there are no new updates on it for 7 years and it might not be relevant anymore. Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•