523710 - Selection in “Target:” field is lost if user goes back to query.cgi from buglist.cgi.

Status: RESOLVED INVALID

(Bugzilla :: Query/Bug List, defect)

Description

[Eiren Smith]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
Build Identifier: Bugzilla 3.4.2 (CVS)

Selection in “Target:” field is lost if user goes back to query.cgi from buglist.cgi.

I get this in my uncustomized Bugzilla 3.4.2 (CVS) installation.

This bug was introduced when we upgraded to Bugzilla 3.4.2 from 3.2.

I didn't find an existing bug for this here on b.m.o.

Reproducible: Always

Steps to Reproduce:
1. Run an Advanced Search. I choose a Product and a Target. Don't choose the first Milestone in your list.
2. After buglist.cgi is done loading, push <Back> in your browser to return to query.cgi.
Actual Results:  
The result for me is that the Target I'd chosen is gone. One of two things happens: Either no Targets are selected now or the first Target in the list (for the still-selected Product) is selected.

Expected Results:  
I expected Bugzilla 3.4.2 to remember the Target I'd specified before I ran the query.

I renamed my bugzilla/template/en/custom/ directory and then re-ran checksetup.pl to be reasonably sure it wasn't from one of my (minor) customizations. I can still reproduce the problem after nullifying the custom/ dir in this way.

I was unable to reproduce this on bugzilla.mozilla.org (3.2.4) today.

I was also unable to reproduce this on on the 3.4.2+ Bugzilla Landfill install (https://landfill.bugzilla.org/bugzilla-3.4-branch/). Hopefully that indicates that it is fixed and not something I've missed in my installation.

Comment 1

[Eiren Smith]

Reproduced in:

  - Safari 4.0.3 in OS X; and
  - IE6 in XP Pro

Comment 2

[Frédéric Buclin]

When you go back, that's the job of your browser to retain the information (in its cache), not Bugzilla. Also, there is no code change between 3.4.2 and 3.4.2+ related to queries/buglist. So it's rather a problem with your local configuration (maybe old templates are still in your brower's cache). And the fact that you cannot reproduce with 3.4.2+ means that this problem, if it existed, is fixed anyway.