The default bug view has changed. See this FAQ.

Disable "Open the Search Tab in the Sidebar when search is invoked" by default

RESOLVED FIXED in seamonkey2.1b2

Status

SeaMonkey
Preferences
RESOLVED FIXED
10 years ago
6 years ago

People

(Reporter: Manuel Reimer, Assigned: Robert Kaiser)

Tracking

Trunk
seamonkey2.1b2
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fixed by bug 410613])

Attachments

(1 obsolete attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.0.9) Gecko/20061222 SeaMonkey/1.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.0.9) Gecko/20061222 SeaMonkey/1.0.7

In current SeaMonkey builds, by default SeaMonkey opens the sidebar when a google search is invoked. I don't think the majority of users really need the sidebar open if searching with google.

I got requests from "SeaMonkey-Newbies" several times, which didn't know about how to get rid of this "auto-opening" of the sidebar. They don't know why SeaMonkey does such unusual things.

As this is definetly a feature, only needed by a few SeaMonkey users, it should be disabled by default.

Reproducible: Always

Steps to Reproduce:
1. Create a new profile
2. Surf to www.google.com
3. Search for something
Actual Results:  
Sidebar will pop up and displays the current search results

Expected Results:  
Sidebar shouldn't pop up. The user decided to search with google and he wants to view the results in the web page, he opened. There is no need to open the sidebar automatically by default.
(Reporter)

Comment 1

10 years ago
Created attachment 253086 [details] [diff] [review]
Patch
[Superseded by bug 410613]
Attachment #253086 - Flags: superreview?(neil)
Attachment #253086 - Flags: review?(neil)
Attachment #253086 - Flags: approval-seamonkey1.1.1?

Comment 2

10 years ago
You thought that was bad? It used to open when you did a google search using the Google website. Now it only opens when you use the search UI.
(Reporter)

Comment 3

10 years ago
It still opens if I'm searching from address bar.

This means, that I get the result in both: Sidebar and content area (the website).

Searching from address bar is a pretty nice feature (just Ctrl+L, enter search term and "Enter"), but I don't think we have to open the web page *and* the sidebar by default. If someone likes the search result in the sidebar, then I think he would also start the search from there. If someone really wants the sidebar to pop up when searching from address bar, then he is able to enable this feature.

Comment 4

10 years ago
Hmm, I always thought that the sidebar reads its results from the web page.
It just saves you from going back to the web page to check out other results.
(Reporter)

Comment 5

10 years ago
Yes, you are right. If I'm searching from sidebar, then my current site is gone and google is opened...

I don't think "bundling" the URL bar search with the sidebar by default is a good idea.

Searching from URL bar is a pretty nice thing. It allowes to initiate a search just with a few shortcuts (Ctrl + L + Cursor up, enter search term, Ctrl + Enter).

Searching on Sidebar is a bit difficult. You only get a "one-liner" which seems to be the page title for most entries. At least I also need the few lines of information about the page, provided by google, to find out if this page is what I'm searching for. So I'll still have to switch back to google, to find more hits, which could be interesting.

If we bundle the two, then SeaMonkey-Newbies may decide to not use the URL-bar-search, as they don't like the sidebar to pop up.

As mentioned above, some people, who got SeaMonkey installed by me, asked me about how they can disable the sidebar. They didn't know about or didn't find the checkbox to turn this off.
I'm pretty sure this is a dupe of a bug that has a patch that neither Neil nor jag were willing to sr.  Hopefully you have better luck.
(Reporter)

Comment 7

10 years ago
I don't know, but I'm still waiting for answer about if I'll get review.

I still think we should not bundle URL-bar search and sidebar search by default. These two are two features, which *may* be combined, but this shouldn't be done by default, as this may cause users not to use powerful URL-bar search as they don't like the Sidebar to pup-up all the time.

And sidebar search needs update/rewrite as it's useless if we don't have the information about the webpages, offered by the search engine.

As we have a very powerful tabbed browsing support, the better way is to open all the entries on the sarch engine in new tabs into background. Then you also have the search result in view until you decide to view your loaded results.
Comment on attachment 253086 [details] [diff] [review]
Patch
[Superseded by bug 410613]

a=me for sm1.1.1, hopefully this gets reviewed.
Attachment #253086 - Flags: approval-seamonkey1.1.1? → approval-seamonkey1.1.1+
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b2pre) Gecko/2007111802 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

While this would make the sidebar less discoverable,
I agree I have yet to learn in which cases this feature would help me :-<
Then, I guess, by default, I would concur to this "bug".

If we want to keep this feature enabled,
may be we could add a (first-time) page/notification/dialog/whatever, something like
"Sidebar is set to auto-open on search, to disable this feature unselect View > Show/Hide > Sidebar, or click here"...
May be with a "Don't ask me again" option.
Like the "secure/unsecure mix" alert or the <about:config> warning...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
(In reply to comment #9)
> "Sidebar is set to auto-open on search, to disable this feature unselect View >
> Show/Hide > Sidebar, or click here"...

Rather:
"Edit > Preferences... > Browser > Internet Search > ..." :-]
That's a lot to ask users to remember. We should just kill it by default.
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
Neil, ping ?
(Assignee)

Comment 14

7 years ago
Manuel, could you update this one for the current code? I really think we should take it now for SeaMonkey 2.1 - esp. in the light that this sidebar isn't that useful any more and could potentially stop working, given someone comes around to switch us to opensearch.
(Reporter)

Comment 15

7 years ago
Already fixed:

http://hg.mozilla.org/comm-central/diff/098388acf16b/suite/browser/browser-prefs.js
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Reporter)

Comment 16

7 years ago
Comment on attachment 253086 [details] [diff] [review]
Patch
[Superseded by bug 410613]

>Index: xpfe/bootstrap/browser-prefs.js
>===================================================================
>RCS file: /cvsroot/mozilla/xpfe/bootstrap/browser-prefs.js,v
>retrieving revision 1.58
>diff -u -8 -p -r1.58 browser-prefs.js
>--- xpfe/bootstrap/browser-prefs.js	20 Jan 2007 20:44:45 -0000	1.58
>+++ xpfe/bootstrap/browser-prefs.js	28 Jan 2007 13:17:56 -0000
>@@ -99,17 +99,17 @@ pref("browser.download.progressDnlgDialo
> pref("browser.download.finished_download_sound", false);
> pref("browser.download.finished_download_alert", false);
> pref("browser.download.finished_sound_url", "");
> pref("browser.download.autoDownload", false);
> pref("browser.download.lastLocation", true);
> 
> // various default search settings
> pref("browser.search.defaulturl", "chrome://navigator-region/locale/region.properties");
>-pref("browser.search.opensidebarsearchpanel", true);
>+pref("browser.search.opensidebarsearchpanel", false);
> pref("browser.search.opentabforcontextsearch", false);
> pref("browser.search.last_search_category", "NC:SearchCategory?category=urn:search:category:1");
> pref("browser.search.mode", 0);
> // basic search popup constraint: minimum sherlock plugin version displayed
> // (note: must be a string representation of a float or it'll default to 0.0)
> pref("browser.search.basic.min_ver", "0.0");
> pref("browser.urlbar.autocomplete.enabled", true);
> pref("browser.urlbar.clickSelectsAll", true);
>Index: suite/browser/browser-prefs.js
>===================================================================
>RCS file: /cvsroot/mozilla/suite/browser/browser-prefs.js,v
>retrieving revision 1.59
>diff -u -8 -p -r1.59 browser-prefs.js
>--- suite/browser/browser-prefs.js	20 Jan 2007 20:45:11 -0000	1.59
>+++ suite/browser/browser-prefs.js	28 Jan 2007 13:17:59 -0000
>@@ -100,17 +100,17 @@ pref("browser.download.progressDnlgDialo
> pref("browser.download.finished_download_sound", false);
> pref("browser.download.finished_download_alert", false);
> pref("browser.download.finished_sound_url", "");
> pref("browser.download.autoDownload", false);
> pref("browser.download.lastLocation", true);
> 
> // various default search settings
> pref("browser.search.defaulturl", "chrome://navigator-region/locale/region.properties");
>-pref("browser.search.opensidebarsearchpanel", true);
>+pref("browser.search.opensidebarsearchpanel", false);
> pref("browser.search.opentabforcontextsearch", false);
> pref("browser.search.last_search_category", "NC:SearchCategory?category=urn:search:category:1");
> pref("browser.search.mode", 0);
> // basic search popup constraint: minimum sherlock plugin version displayed
> // (note: must be a string representation of a float or it'll default to 0.0)
> pref("browser.search.basic.min_ver", "0.0");
> pref("browser.urlbar.autocomplete.enabled", true);
> pref("browser.urlbar.clickSelectsAll", true);
Attachment #253086 - Flags: superreview?(neil)
Attachment #253086 - Flags: review?(neil)
Assignee: nobody → kairo
Depends on: 410613
Flags: in-testsuite-
Whiteboard: [fixed by bug 410613]
Target Milestone: --- → seamonkey2.1b2
Attachment #253086 - Attachment is obsolete: true
Attachment #253086 - Attachment description: Patch → Patch [Superseded by bug 410613]

Comment 17

6 years ago
Turn it into an option, rather than disable it by default
(Assignee)

Comment 18

6 years ago
(In reply to comment #17)
> Turn it into an option, rather than disable it by default

It always has been an option, and it still is. No idea what you are talking about.
You need to log in before you can comment on or make changes to this bug.