Closed
Bug 1202139
Opened 10 years ago
Closed 10 years ago
search engine option
Categories
(Firefox :: Untriaged, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: snehasb21, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150826023504
Steps to reproduce:
opened new tab. did not want the outlines of bookmarks. so opened blank page. should provide an option to see search engine.
Actual results:
got a blank page
Expected results:
want search engine on new tab as an option instead of the blank page.
Define your default search engine in the options, then set about:config > browser.newtab.url = about:home.
You're done.
(In reply to Loic from comment #1)
> Define your default search engine in the options, then set about:config >
> browser.newtab.url = about:home.
> You're done.
Okay.
![]() |
||
Comment 3•10 years ago
|
||
Sneha, is the problem solved? Should this bug be closed?
QA Whiteboard: [bugday-20150907]
Flags: needinfo?(snehasb21)
(In reply to Sneha from comment #2)
> (In reply to Loic from comment #1)
> > Define your default search engine in the options, then set about:config >
> > browser.newtab.url = about:home.
> > You're done.
>
> Okay.
Thanks. The problem has been solved.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(snehasb21)
Resolution: --- → WORKSFORME
(In reply to [:Aleksej] from comment #3)
> Sneha, is the problem solved? Should this bug be closed?
Yes, the problem has been solved successfully. I have changed the status of the bug to "RESOLVED WORKSFORME".
(In reply to Sneha from comment #2)
> (In reply to Loic from comment #1)
> > Define your default search engine in the options, then set about:config >
> > browser.newtab.url = about:home.
> > You're done.
>
> Okay.
Another comment: browser.newtab.url will be removed after Firefox 41 (bug 1118285) to lower malware hijacking so you will have to install an add-on to bring back this pref (like https://addons.mozilla.org/en-US/firefox/addon/new-tab-override/).
You need to log in
before you can comment on or make changes to this bug.
Description
•