Closed
Bug 45813
Opened 26 years ago
Closed 24 years ago
Folders with unread messages are not bolded after theme switch
Categories
(Core Graveyard :: Skinability, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: fenella, Assigned: hyatt)
References
Details
(Keywords: polish)
Win32 (2000-07-18-11 M17)
1. Launch Messenger
2. Switch it to Classic theme
3. Form the Thread pane, observe the Unread message
Actual result: Unread message does not show bolded text
Expected result: It should be bolded.
Linux and Mac not tested due to bug45336
4. Also check the folder pane
Actual result: Folders' name with Unread message is NOT bolded.
Expected result: Folder name should be bolder when there exists a Unread message
Since I do not want to run the risk of having a dup. I am putting this in the
same bug because it is also bold text problem. Developer, if you want a separate
bug, please let me know. I'll file one.
I think this has to do with Reflesh problem. Because when I exit and relaunch
Messenger uisng the Classic theme, the bolded text shows up in both the Folder
pane and the Thread pane
Sending Classic Theme bugs to Brendan for management.
Assignee: hangas → bdonohoe
Comment 4•26 years ago
|
||
This is not theme specific. If you switch from Classic to Modern, the same
problem occurs. Only quitting and relaunching the application will cause
the bolding to come back.
Putterman, can you investigate what's going on here?
Assignee: bdonohoe → putterman
Comment 5•26 years ago
|
||
reassigning to ben. It looks like many style rules are not working after
switching. cc'ing mscott. I'm wondering if this is related to the crash when
selecting a message after switching a skin bug since the moment I try to do
something, I crash.
Assignee: putterman → ben
Summary: Unread messages are NOT bolded in thread pane → Classic: Unread messages are NOT bolded in thread pane
Comment 7•25 years ago
|
||
Theme switch issue. Updating summary, moving to skinability.
Component: Themes → Skinability
QA Contact: pmac → blakeross
Summary: Classic: Unread messages are NOT bolded in thread pane → Unread messages/folders are no longer bolded after theme switch
Testing under 6.01, new messages in thread pane are properly "bolded" (I'm
sorting by date). However, folders with unread mail in folder pane don't get
"bolded"
Comment 11•25 years ago
|
||
Marking nsbeta1-, adding polish and dogfood keywords. This is one of those
things that should just work. Marking nsbeta1- because I don't think Ben will
get to this for beta1.
Comment 12•25 years ago
|
||
Is this really only an NT issue? Mozilla1.0 nomination.
Keywords: mozilla1.0
Comment 13•25 years ago
|
||
Marking nsbeta1- bugs as future to get off the radar.
Target Milestone: --- → Future
Comment 14•25 years ago
|
||
converting from dogfood to catfood. This isn't preventing anyone from doing work.
Comment 15•25 years ago
|
||
nav triage: reassigning to Steve Morse, targeting mozilla0.9.2, nsCatFood+
Comment 16•25 years ago
|
||
Unread message part of this report is working for me. They indeed remain bold
after a theme switch. However I am seeing the second item mentioned in the
bug report, namely the the folder which contains the unread message is no longer
bold after the switch.
Updating summary from
Unread messages/folders are no longer bolded after theme switch
to
Folders with unread messages are not bolded after theme switch
OK, reading further I see that pchen reached the same conclusion on 2001-02-08.
But he never updated the summary line to reflect that.
No longer blocks: 68973
Summary: Unread messages/folders are no longer bolded after theme switch → Folders with unread messages are not bolded after theme switch
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 17•25 years ago
|
||
nav triage: not an rtm stopper, esp since in commercial builds, we may require
you to restart in order to see the new theme take effect. moving to m1.0.
Target Milestone: mozilla0.9.2 → mozilla1.0
Comment 18•24 years ago
|
||
More realistic milestone since dynamic theme switches are not being supported.
Target Milestone: mozilla1.0 → Future
| Assignee | ||
Comment 20•24 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•