52213 - Changes to Adv Search tab

Status: VERIFIED FIXED

(SeaMonkey :: Search, defect, P2)

Description

[johng]

Usability results lead us to 3 high-priority changes in the Adv Search tab:

1) Add the following text above the "Search Engines" list:
Choose search engines then click Search

2) Remove the "Customize" button at the bottom of the tab (only shows when you
are viewing the search engines - it currently goes away when you have search
results).  This button totally confused users since they thought they had to
click it everytime they changed anything in the list (like an OK button).

3) Add to the list of categories in the drop down menu (within [       \/ ]:
Edit Categories ....

Within this list, there should be a divider between "Edit Categories ..." and
the list of categories, would prefer this to be at the bottom of the list but
probably have to be at the top just below "All Engines" (overlay issues with
rdf).  When the user clicks on "Edit Categories ...", the dialog that you used
to get with the Customize button opens.  The drop down then reverts back to
whatever was selected last (1st choice) or, if you have to hard wire it, it
should revert to "All Engines".

assigning to matt, recommending a P1 or P2 priority with a nsbeta3+.  Even
though only some users will be using this advanced tab, this is a competitive
differentiator compared to IE, a high profile feature.

Comment 1

[johng]

nav triage team:
nsbeta3+, P1

a couple mroe details:
new text should include a comma, namely:
Choose search engines, then click Search

Also, if there are difficulties in adding the "Edit Categories ..." to the rdf 
list, you can instead just keep the button at the bottom and change the text to:
Edit Categories ...

Comment 2

[lchiang]

per PDT team:  this is a P2 priority bug.  If you believe this to be a P1,
please specify the reasoning per the P1 criteria list.  Thanks.

Comment 3

[Robert John Churchill]

> new text should include a comma, namely:
> Choose search engines, then click Search

Ah, no offense, but Marketing shouldn't be allowed to create any text phrases,
as it seems that they often barely understand english.

This text looks bad in regards to where its places in the search panel and is
actually incorrect as the user doesn't "choose search engines, then click
search"... the user also needs to type in some text to search for.

Please consult with a doc person to come up with some text that works... and
better placement of the text in the search panel would be nice also.

Comment 4

[lchiang]

I'll cc: verah (docs) for suggested wording and such.

Comment 5

[matt]

Leaving open but checked in the code.
Will close if there are no other changes.

Comment 6

[verah (gone)]

Actually, I reviewed this already... currently users see the search field first, 
the search button second, and the list of search engines third or maybe 
fourth... and that's a problem. Apparently they expect UI elements to appear in 
the order in which they're needed (silly users!). But since we can't move things 
around at this point to put the list of search engines second (or first), we're 
adding this text.

Since it's *under* the search field, they will have already filled in the search 
field. This is the way things are often done in dialogs... that is, explanatory 
text next to a checkbox or radio just tells you what to do with that checkbox or 
radio, it doesn't tell you all the preceeding steps.

But I agree that the placement is weird -- I thought it was going to be at the 
top of the list of search engines -- in other words, in the box titled Search 
Engines, right above the first engine listed (AOL Search). Can this happen?

P.S. Now, John may have his faults -- he gets riled from time to time, being 
from Kentucky and all -- but I've found his command of English to be reel good.

Comment 7

[matt]

closing out this bug based on verah's comments

Comment 8

[sairuh (rarely reading bugmail)]

mass-verifying claudius' Fixed bugs which haven't changed since 2001.12.31.

if you think this particular bug is not fixed, please make sure of the following
before reopening:

a. retest with a *recent* trunk build.
b. query bugzilla to see if there's an existing, open bug (new, reopened,
assigned) that covers your issue.
c. if this does need to be reopened, make sure there are specific steps to
reproduce (unless already provided and up-to-date).

thanks!

[set your search string in mail to "AmbassadorKoshNaranek" to filter out these
messages.]