Closed
Bug 84581
Opened 24 years ago
Closed 24 years ago
Not refresh right away after change the themes from modern to classic
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
People
(Reporter: huang, Assigned: hewitt)
Details
(Keywords: regression)
Used 06-07-13-0.9.1 build
Not refresh right away after change the themes from modern to classic until
relaunch again
1) Crate a new profile
2) Go to the preference change the themes from default modern to classic
3) No refresh the change from modern to classic until relaunch again
Expected results: Should refresh the change from modern to classic right away
without relaunch again...
P.S. Also, the OK button seems not working when switching between modern
& classic.....
| Reporter | ||
Comment 1•24 years ago
|
||
adding nsbeta1 & regression for the keywords.....
Keywords: nsbeta1,
regression
Summary: Not refresh right away after change the themes from modern to classic → Not refresh right away after change the themes from modern to classic
| Reporter | ||
Comment 2•24 years ago
|
||
Lisa mentioned that this is dup of bug 81970
*** This bug has been marked as a duplicate of 81970 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Karen, <<the OK button seems not working when switching between modern
& classic.....>>, this OK button has been reported couple weeks ago
in the bugzilla bug database. I will let you know the bug number for that.
Thanks!
Karen, <<the OK button seems not working when switching between modern
& classic.....>>, this OK button has been reported couple weeks ago
in the bugzilla bug database. I will let you know the bug number for that.
Thanks!
Karen, the bug 83419 also applied to the "OK and Cancel" buttons as well.
http://bugzilla.mozilla.org/show_bug.cgi?id=83419
| Reporter | ||
Comment 7•24 years ago
|
||
Then, you probably need to change bug 83419 UNCONFIRMED to NEW and update the
summary for applying OK & Cancel buttons.-- just suggestion!! :-)
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•