282757 - Default "Advanced Search" is For Duplicates Only

Status: RESOLVED INVALID

(bugzilla.mozilla.org :: General, defect)

Description

[Jerry Baker]

When you open the "Query" page and then select "Advanced", the search defaults
to only include duplicates. There shouldn't be a default selected.

Comment 1

[Dave Miller [:justdave]]

Actually it has the blank resolution selected also, which means "any open bug
plus anything resolved as a duplicate"

Comment 2

[Jerry Baker]

As a side note, where's the search form that doesn't default to looking for only
open bugs? I can't see a way to set that as my default.

Comment 3

[Dave Miller [:justdave]]

OK, Gerv, how does he do this? :)

I don't see a way to do that with the current UI without pulling all 285000 bugs
from the database at the same time.

The apparent way to do this with the current UI is:

Clear everything on the form, then check the box for "and remember these as my
default search options", then click search.

Comment 4

[Gervase Markham [:gerv]]

Yeah, you can do that. It saves your defaults before it does the search so as
soon as the top of the results page appears, you can close the browser window or
click Back or whatever.

It's an edge case :-)

Gerv

Comment 5

[Jerry Baker]

But the query will continue to execute on Bugzilla. Why is the default to limit
the search instead of to let people choose how they, as an individual, would
like it to default?

Comment 6

[Gervase Markham [:gerv]]

> But the query will continue to execute on Bugzilla. 

No; your browser will close the connections when you close the window or
navigate away from the page. This results in the webserver sending a signal to
the process, which we catch and abort on.

> Why is the default to limit
> the search instead of to let people choose how they, as an individual, would
> like it to default?

Because most people, particularly newbies, just type into the top box and press
Enter. 

Gerv

Comment 7

[Jerry Baker]

I thought that was the whole reason for making the default the "simple" search.
Why both then?

I dunno about the execution halting. If I make a change to a bug, and press stop
on my browser before anything happens, the changes are still committed. I've
seen it several times.

Comment 8

[Gervase Markham [:gerv]]

Changes to a bug work differently. 

We added special code to catch the signals and abort (or continue; I forget
which way round we did it) for some scripts. So the fact that the behaviour is
different is known.

Gerv