Closed
Bug 119836
Opened 23 years ago
Closed 23 years ago
Can't save status when check and uncheck columns in History dialog box
Categories
(Core Graveyard :: History: Global, defect, P4)
Core Graveyard
History: Global
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 123285
People
(Reporter: gilbert.fang, Assigned: gilbert.fang)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 Reproducible: Always Steps to Reproduce: Pls strictly operate the following steps Machine:SunOS racing 5.9 s81_51 sun4u sparc SUNW,Sun-Blade-100 Broswer:Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4) Gecko/20011206 Netscape6/6.2.1 BuildID: 2001112114 Step of reproduce: 1.Select menu Tasks|Tools|History to open the History window 2.In History window,click right top corner to check columns,such as First Visited and Hostname. 3.Uncheck First Visited and Hostname. 4.Check First Visited and Hostname again. 5.Close History window. 6.Open the History window again. Actual Results: Actual Results: Columns First Visited and Hostname is unchecked Expected Results: Expected Results: After step #6,dialog should be save History window's status,in other word,columns First Visited and Hostname should be checked
Assignee | ||
Comment 1•23 years ago
|
||
I have found the incorrect code. It is the outliner id=historyOutliner which should set an attribute "Hidden" false instead of remove it when user uncheck the corresponding items . Pls confirm the bug and assign it to me. I will fix it quickly.
Assignee: blaker → Gilbert.Fang
Priority: -- → P4
Comment 2•23 years ago
|
||
confirmed with a 2002011808 MacOSX build
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 3•23 years ago
|
||
It is the same with 123285. I am so busy recently that I did not post a patch. Thanks to Blake Ross. *** This bug has been marked as a duplicate of 123285 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•