The Change Columns behaviour seems to be stuck when using FireFox

RESOLVED INVALID

Status

()

RESOLVED INVALID
11 years ago
11 years ago

People

(Reporter: martin.ofarrell, Unassigned)

Tracking

2.22.1
x86
Windows XP

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

The Columns displayed for a search seems to be 'stuck'.
By this I mean that when it is set to show e.g. 'Summary' and 'Full Summary'
columns.
If I run a search it displays these both these columns.
Then I change it to turn off one of the cols. e.g. 'Full Summary' 
The change never takes effect.
I still see both columns, and if I go back to see list of displayed cols
I see that both are checked.
This applies to any of the cols. - 'Full Summary' is just an example.

Reproducible: Always

Steps to Reproduce:
1.Start Mozilla Firefox browser and point it our Bugzilla installation.
2.Run a query e.g. the standard default one for all Open bugs
3.Observe that both 'Summary' and 'Full Summary' are shown in search output.
4.Now use 'Change Columns' and disable the 'Full Summary'.
5.Click 'Change Columns' to effect the change.
6. Observe that both 'Summary' and 'Full Summary' are still displayed.
7. Click 'Change Cols. again.
8. Observe that 'Full Summary' is still checked.

Actual Results:  
included above ....

Expected Results:  
Expected at step 6 that I would not see 'Full Summary' column
Expected at step 8 to see that 'Full Summary' to be un-checked.

When I use Firefox to view Bugzilla's own bug list, I don't encounter the above issue.

When I use Internet Explorer version 6.0 everything works fine
when I access our bug list in the manner described above.
(Reporter)

Updated

11 years ago
Version: unspecified → 2.22.1
(Reporter)

Comment 1

11 years ago
Seems to have been an issue with cookies in Firefox

I cleared the cookies and then re-tried the above
and things now work as expected.

==========================================================
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.