User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20100920 Fedora/3.6.10-1.fc13 Firefox/3.6.10 Build Identifier: 4.1 When doing an Advanced Search, if the browser's back button is used to return from buglist.cgi to query.cgi, fields/values that were originally selected can change automatically. For example, if I got to the Advanced Search form and select a variety of fields values (say Classification, Product, Component, and Version) and then hit the Search button, I may or may not "find" any bugs. Regardless, if I hit the back button to return to the form, some of the originally selected values can either change or get unselected. This was observed using Internet Explorer 8.0.7600.xxxxxx on Windows 7 and also using Google Chrome 7.0.517.41 on Fedora 13. It does NOT appear to be a problem for Firefox on either of those two systems. Reproducible: Always Steps to Reproduce: I was able to reproduce this on the latest version of Bugzilla (4.1) with a very minimal set of classifications/products/components/versions defined, but here is an example of how I reproduced it at bugzilla.mozilla.org: 1. Go to the Advanced Search form (query.cgi) 2. Select some combination of field values, e.g.: - Classification: Server Software - Product: Bugzilla - Component: Query/Bug List - Version: 3.6.2 - Status: All open statuses 3. Hit Search button 4. Hit browser's back button Actual Results: At this point (back on the Advanced Search form), the values above should still be selected, but the values I actually see selected are: - Classification: Server Software - Product: AUS - Status: All open statuses If I hit the Search button again and then go back again and I see the selected product change to addons.mozilla.org. Expected Results: Returning from a buglist to the Advanced Search form should obviously not cause any of the selected fields/values to change.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
dupe of bug 584742?
(In reply to comment #2) > dupe of bug 584742? I originally thought it might be the same problem (or related), but the "Hacky Fix" attached there does not resolve this problem.
Guy, could you fix this, do you think? There's also a chance it will be coincidentally fixed by bug 636416.
i'll take a look at this, sorry for the lag on it.
You need to log in before you can comment on or make changes to this bug.