Closed
Bug 86905
Opened 23 years ago
Closed 23 years ago
Search results not displayed in the Search Tab
Categories
(SeaMonkey :: Search, defect)
SeaMonkey
Search
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: peterjez, Assigned: matt)
References
()
Details
(Keywords: regression, smoketest)
1) Open the latest build of Netscape 6 on your Mac
2) Close the sidebar
3) Enter "gameboy advance" into the location bar
4) Click on the Search button
5) Notice the sidebar open and display the search tab, but no results appear.
Reporter | ||
Comment 1•23 years ago
|
||
A couple notes about search on the Mac:
1) This problem occurs only with certain search engines.
-Works for Lycos.
-Sidebar Search results aren't refreshed when using Altavista
-Sidebar Search results become blank when using Excite
Reporter | ||
Comment 2•23 years ago
|
||
The sidebar results panel doesn't open at all on Linux when using url bar
search.
OS: Mac System 9.x → All
Hardware: Macintosh → All
Reporter | ||
Comment 3•23 years ago
|
||
Adding smoketest and regression keywords. I think this problem has been on Mac
for a while, but the url bar search and sidebar search results were working fine
on Linux yesterday (6/19/2001).
Keywords: regression,
smoketest
this might have to do with bugscape bug
http://bugscape.mcom.com/show_bug.cgi?id=5877
Comment 5•23 years ago
|
||
some of the sherlocks are broken and some of the sherlocks are missing on
Mac/Win. this sounds like two other bugs.
This bug was reported for NS6, but must be confirmed under a Mozilla build to be
valid here. Reporter, please retest under Mozilla.
Since this is still only reported for Netscape 6, marking invalid until someone
tests it under Mozilla to get it off the unconfirmed list.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Comment 8•23 years ago
|
||
marking this VERIFIED Invalid but only because it was actually long ago fixed.
Greg: I don't get your logic. i don't know if you've done this to other bugs but
had this turned out to still be a bug no one would have ever known. You've
defeated the whole point of the 'unconfirmed' status. A bug should sit in that
bucket until someone can definitively say it happens in Mozilla (-->New) or it
does not happen in Mozilla(-->invalid). By shoving over to the invalid bucket
prematurely(without testing) you've pretty much consigned it to oblivion.
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•