Closed
Bug 32909
Opened 25 years ago
Closed 25 years ago
[search ui]search results no longer persistent
Categories
(SeaMonkey :: Search, defect, P3)
SeaMonkey
Search
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: german, Assigned: johng)
Details
(Whiteboard: [nsbeta2-])
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; N; Win98; en-US; m14) Netscape6/6.0b1
BuildID: 2000032211 and also 20000320xx
Once the category popup on the search panel gets clicked the search results
disappear forever
Reproducible: Always
Steps to Reproduce:
1.open sidebar search panel
2.type in a search
3.wait for results to show up
4.click to select a different category
Actual Results: The search results list gets wiped out and replaced by a search
engine list. Users can no longer conveniently access the most recent reults set
Expected Results: The results should stay available until another search is
actually started
Persistency of immediate recent search results is what will make users use the
sidebar for searches.
Its the single biggest usability benefit we found when testing Search UI, almost
all users enjoyed goign back and forth across search results. We believe users
would see as lower priority to change the category setups everytime they launch
a search. Probably a very large portion of typical Netscape consumers will not
want to customize search engines at all. Giving up persistent search results for
that means setting the wrong priority.
by the way I like the running status inidcator added to the 'Stop' button.
Keywords: beta2
Target Milestone: ---
Comment 2•25 years ago
|
||
German, if there are any search results, they persist until the user changes the
category, at which time the list of engines is shown. If the user is changing
categories, the implication is that they are about to do another search.
By automatically showing the engines in this manner, users get a better feel for
the ability to search multiple engines. Also, it helps out Netcenters business
model.
Assignee: matt → rjc
Comment 4•25 years ago
|
||
Additional note: this is how Sherlock works.
This is not resolved, reopening bug. You can't get off that easy, Robert. :-)
With all the testing results and expertise that German brings to the table,
Robert, Ben and German need to come together on this as well as the entire
search UI design.
We have a little time for beta2 - let's work through this the right way and make
sure we get input from the smartest people on this before we say it is done. It
will take less time to agree upfront on big UI changes then it will to reiterate
over what is checked in after the fact.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 6•25 years ago
|
||
John, this has always been the plan.
If you want this bug to track the search UI, great, its yours.
Assignee: rjc → johng
Status: REOPENED → NEW
PDT needs more info on how this is a beta stopper. johng, can you explain? Is
this still a problem with latest builds?
Whiteboard: [NEED INFO]
Putting on [nsbeta2-] radar. Would like to get in for beta2. But may be held
back by Netcenter/CPD Search negotiations. :-)
Whiteboard: [NEED INFO] → [nsbeta2-]
Looking at most recent UI, I'm satisfied with Robert's discription that this is
currently working the way it should.
Marking Invalid.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•