76204 - Display search results in a floating window (don't take over the browser)

Status: NEW

(SeaMonkey :: Search, enhancement)

Description

[pbergsag]

From Bugzilla Helper:
User-Agent: Mozilla/4.76 (Macintosh; U; PPC)
BuildID:    20010416

Here is the issue: if anyone has used the Apple Sherlock you will more easily 
understand my critique of Mozilla's version of Sherlock. Is it possible to 
improve searches so that the rsults of a search do not take over the main browser 
window. Would it be possible to place the results of searches in a floating 
window (similar to banner adds) so that the page you are viewing is not replaced 
with search results and when you surf to a site from the search results page, all 
the contents of the search are not replaced with the new page surfed to.

Here, in other words is what I wish for in the search engine. 
1. Enter search criteria.
2. Have a new floating window pop up to display the results of the search. The 
main browser window will remain unchanged, staying at the present site.
3. Click on a link in the floating search window and the Main browser window will 
take you to the new site selected from the floating search window. The floating 
search window will be left unchanged, ready for another selection if needed, or 
closed if the search is ended.

(I hope my wish has been understood. To gain an better idea of what I am wishing 
for, try the Sherlock search engine on a Mac if you can.)

Reproducible: Didn't try
Steps to Reproduce:
This is a wish for an enhancement for the Mozilla search engine so please ignore 
reproducibility.

Comment 1

[Claudius Gayle]

sounds like what you're asking for is the Stand Alone Search window. I miss it too. From
the toplevel 'Search' menu you will see listings for 'Search the Web' and 'Search Bookmarks/
History'. Select bookmarks and history. This window is the shell of what once was the stand
alone search window. Used to be, if you selected 'search the web' you'd get this window too.
It was removed due to lack of development resources.

I don't know what the right resolution would be for this bug, i doubt (maybe I'm wrong though)
that there is a bug that says 'bring back stand alone search' already out there.

Comment 2

[pbergsag]

Yes, I think stand alone search is what I am wishing for. Apple's sherlock is so 
much more useful because it doesn't take over the browser, that is it is stand 
alone. I would like to be able to use Mozilla search engine, but if it does not 
have the stand alone function I will have to use Apple's Sherlock, which btw 
crashes or functions less than perfectly with Mozilla (is it interfering with 
Mozilla's search engine?) Sherlock functions perfectly with NS 4.77.

I wish I was able to program, then I would make search "stand alone". Can anyone 
help to nominate this bug so others review it to see if it warrants attention? :)

Comment 3

[Blake Ross]

reassigning matt's old bugs to default owner.

Comment 4

[Erich 'Ricky' Iseli]

How's this bug looking like in the light of tabbed browsing?

Comment 5

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 6

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 12

[Karsten Düsterloh]

Still worth pondering about.