Closed Bug 19254 Opened 25 years ago Closed 23 years ago

"New" flag and "unread" state in folder pane should propagate to parents

Categories

(SeaMonkey :: MailNews: Message Display, defect, P2)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.6

People

(Reporter: phil, Assigned: sspitzer)

References

(Blocks 1 open bug)

Details

(Whiteboard: [minus][nsbeta1+ 2/21])

Attachments

(1 file)

patch.
10.01 KB, patch
Bienvenu
: superreview+
Details | Diff | Splinter Review 
In 4.x, folder names are bold when the folder or one of its children contains
unread messages. But the "new" green arrow seems to only apply to the folder
itself, not children. This means that if a subfolder has new messages, it's hard
to tell that it has received new messages. We should fix this in mozilla.
QA Contact: lchiang → fenella
Status: NEW → ASSIGNED
Target Milestone: M12
Reminder to myself:
When this bug is fixed, refer to bug 17841 to check the bolded text in the
parent folder (when the unread message only exists in its subfolder).
Target Milestone: M12 → M13
let's try M13.
Target Milestone: M13 → M15
Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
reassigning to gayatrib.
Assignee: putterman → gayatrib
Status: ASSIGNED → NEW
Blocks: biff
Status: NEW → ASSIGNED
*** Bug 36385 has been marked as a duplicate of this bug. ***
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Moving to future milestone.
Target Milestone: M17 → Future
Scott, how do mozilla users know that a subfolder contains new mail? If the
answer is "they don't" then I'm a little nervous about moving this to Mfuture.
I object to moving this to the future! How in the hell will people know when new
messages have been filtered to a subfolder if collapsed?  When you decided not
to include cross folder navigation in this release, this (parent getting new
flag) was the only hope for those of us who regularly filter to a sublevel. 
you can always mark as nsbeta3 if you want.
Keywords: nsbeta3
adding correctness keyword and making it P1.
Keywords: correctness
Priority: P3 → P1
Keywords: mail2
- per mail triage.  cc: kmurray, marek - this is one of the bugs for marek's 
team to help with (mark m21 to denote this)
Whiteboard: [nsbeta3-]
Target Milestone: Future → M21
correcting.  + per mail triage.  SusEng team will help with this bug.
Whiteboard: [nsbeta3-] → [nsbeta3+]
P4 per mail triage
Priority: P1 → P4
PDT downgrading to [nsbeta3-].
Whiteboard: [nsbeta3+] → [nsbeta3-][minus]
Nominating for mozilla 1.0.
Keywords: mozilla1.0
sorry for the extra email. Removing mail2 keyword.
Keywords: mail2
nominate for 6.5, added mail3 keyword
Keywords: mail3
*** Bug 60229 has been marked as a duplicate of this bug. ***
*** Bug 60229 has been marked as a duplicate of this bug. ***
adding nsbeta1+ and changing summary to also track the unread state. I wasn't
sure if there was already a bug to do this.
Keywords: nsbeta1
Priority: P4 → P2
Summary: "New" flag in folder pane should propagate to parents → "New" flag and "unread" state in folder pane should propagate to parents
Whiteboard: [nsbeta3-][minus] → [nsbeta3-][minus][nsbeta1+]
moving to mozilla0.8 milestone.
Target Milestone: --- → mozilla0.8
reassigning to chuang.
Assignee: gayatrib → chuang
Status: ASSIGNED → NEW
I don't think this will be done by 0.8, so changing milestone.
Target Milestone: mozilla0.8 → mozilla0.9
marking nsbeta1- and moving to future milestone.
Keywords: nsbeta1, nsbeta3 → nsbeta1-
Whiteboard: [nsbeta3-][minus][nsbeta1+] → [minus][nsbeta1+ 2/21]
Target Milestone: mozilla0.9 → Future
*** Bug 72896 has been marked as a duplicate of this bug. ***
*** Bug 77106 has been marked as a duplicate of this bug. ***
*** Bug 82990 has been marked as a duplicate of this bug. ***
Cc'ing myself. Would be nice if this bug could be fixed soon, if you have
several mail accounts with lots of subfolders you have to go through all the
folders which is quite painful on a 'slow' (350MHz, 200MB) machine.
*** Bug 88800 has been marked as a duplicate of this bug. ***
*** Bug 90038 has been marked as a duplicate of this bug. ***
QA Contact: fenella → laurel
reassigning to sspitzer
Assignee: chuang → sspitzer
working on the fix, testing it now...
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.6
Comment on attachment 52813 [details] [diff] [review]
patch.

sr=bienvenu
Attachment #52813 - Flags: superreview+
adding granrose, he's been wanting this for a while.
fixed.  this also works for filters.

if you have a > b, and a is closed, and you filter into b, a becomes bold.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
looking at phil's original summary, I only fixed the "unread" part of this bug, 
not the "new".

bienvenu / putterman, do we also want to fix the "new" part of this bug?  if 
so, I'll spin up the new bug.

Does this apply to the thread pane as well?
this just happens in the folder pane.
Adding jglick for her opinion.

My opinion is that we should propagate the new flag (this seems to be the
original intent of Phil when he filed the bug as well).  If you are filtering to
subfolders and biff goes off, we are currently in a state where you would have
no idea what folder to check.
Agree with putterman. The green arrow "new" flag should appear on the parent 
folder if a sub folder contains a "newest" message but the parent folder is 
closed.
Since this does not apply to the thread pane, is there an existing bug for that,
or should I file a new one? It makes sense for the parent thread to be bold if a
new message is contained within that collapsed thread. I believe 4.x did this,
and I think it should be supported.
yes, there are existing bugs for the thread pane. don't know the numbers off 
hand.
seth, can we take advantage of the code for this to apply it to the thread pane?
bug 74357 is the thread pane bug.

bug 76414 is related to the green "newest" indicator icon for threads.
http://bugzilla.mozilla.org/show_bug.cgi?id=74357 has discussion about what to
do in the thread pane.
OK using oct26 commercial trunk build: win98, linux rh6.2 and mac OS X
New green arrow icon doesn't show at collapsed parent, but unread/bold does. I
checked 4.x and it doesn't show new green arrow at collapsed parent level either.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: