Closed Bug 21094 Opened 25 years ago Closed 23 years ago

[FEATURE] Make select thread work

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
Future

People

(Reporter: leaf, Assigned: sspitzer)

References

Details

(Whiteboard: [dogfood-][nsbeta1+ 1/28]) 

Deleting threads is a real PITA. There doesn't seem to be any way at all to
select and delete more than a single message.
Assignee: phil → alecf
Summary: Please make select thread work. → [FEATURE] Make select thread work
Reassign to alecf, cc putterman
OS: Linux → All
Hardware: PC → All
Blocks: 10791
QA Contact: lchiang → fenella
Does anyone with an inbox with > 100 messages really believe this is not
dogfood?
You're welcome to mark it dogfood if you think it is. Personally, I have ~2000
messages in my inbox and I'm limping along, modulo bug 20634
1058 messages and didn't even know the feature existed :)

Seriously though, there are a bunch of threading issues that should probably be
tackled pre-beta.  I'd rather see this as one of those. But if others disagree I
can work on it.
Status: NEW → ASSIGNED
I use this all the time but if we mark this dogfood, it's going to have to be
one of the 5 bugs that don't make dogfood. :)
IMO this bug is not in the same league as the others marked PDT+. Scott, if you
have time for this before beta, that's great, but I wouldn't hold beta for this.
OK, I'm reassigning to me.  If I do more threads work and this falls into it I
will get this done pre-beta.
Assignee: alecf → putterman
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Target Milestone: M17
Let's say M17, but as I said before, if it turns out that this is part of the
thread work I'm currently doing, it will be sooner.
So, basically, mozilla mail is useless to me until april or may?

bummer.
d'oh, i'm an idiot, last comment was meant for a different bug.
[FEATURE] bugs past M16 are OUT for this release.  Marking M20.  If you disagree 
with this action, please help me explain it to the PDT.
Target Milestone: M17 → M20
There is a difference between a feature like the standalone message window which 
will take multiple weeks and touch many files and a feature such as this which 
will hopefully only take a day or less, touch much less files, and is no 
different than other bugs.  If we want this capability, I"m not sure we should 
be moving this to M20.
Target Milestone: M20 → M17
This is dogfood for me. When a thread has run its course, i'd like to be able to
Alt-Shift-A, or whatever, to select the entire thread for removal or copying to
an archive folder. 

Being limited to single-message operations is a big hassle. It seems that this
*almost* works now, in that i can get an entire thread selected by selecting the
first reply in the thread, and then shift-selecting the first message of the
thread. So, in a way, this is more of a bug than a feature, since it already
partially works =)
leaf, do you want to mark this as dogfood?  I think this needs to be considered 
a feature rather than a bug even though I don't think it will be too much work.
well, it's dogfood for me, certainly.
Keywords: dogfood
Marking as nsbeta2 as well then since I'm not sure we should hold M16 for it but 
it might be worth considering for feature work for beta.
Keywords: nsbeta2
phil to gather more info on this.
Whiteboard: [NEED INFO]
Putting on [nsbeta2-] radar.  This feature is out completely for PR2 and RTM, 
please move to MFuture
Whiteboard: [NEED INFO] → [nsbeta2-][dogfood-]
I want this reconsidered for nsbeta2+. It really sucks not having this -- makes 
seamonkey mail much harder to use than 4.x, especially when you receive a large 
number of messages. Waterson and Bienvenu agree that this should be in.
Whiteboard: [nsbeta2-][dogfood-] → [dogfood-]
I'd consider this for RTM.  I don't think this is necessary for beta2.
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [dogfood-] → [dogfood-][nsbeta2-]
I'm setting myself up to get flamed.  I'm moving to the future milestone.
Please mark nsbeta3 and apply (correctness, polish, crash, performance, or
footprint) if you think this should be in the beta.  Despite my earlier comments
about this not being a big feature I'm having trouble justifying getting this
into this release.
I for one use this on a regular basis do delete large chunks of mail in one 
sweep.... You can't assume that everyone has the exact same pattern of reading 
mail as you :(

How hard do you think this is?
It seems like the approach would be somewhat simple:
- walk up to the toplevel message in the current thread, and expand it and all 
it's children
- select all the items in that DOM subtree..

that might be slow though, I don't know.
Keywords: nsbeta3
there was no assumption in my comments about useability patterns or ease of
implementing.  Since we are talking about nsbeta3, I was just pointing out that
this doesn't seem to fit any of the criteria for which we are using to determine
bugs to work on.  It's not correctness.  It's not polish. It's not performance.
 It's not a crasher. And it's not footprint.  Perhaps useability though I would
argue we have much bigger thread useability bugs to fix than this one.
Mail triage team is marking nsbeta3-
Whiteboard: [dogfood-][nsbeta2-] → [dogfood-][nsbeta2-][nsbeta3-]
Target Milestone: M17 → Future
*** Bug 55609 has been marked as a duplicate of this bug. ***
nominating mail3
Keywords: mail3
reassigning to sspitzer
Assignee: putterman → sspitzer
Status: ASSIGNED → NEW
moving to mozilla0.9 and marking nsbeta1+
Keywords: nsbeta2, nsbeta3 → nsbeta1
Priority: P3 → P2
Whiteboard: [dogfood-][nsbeta2-][nsbeta3-] → [dogfood-][nsbeta1+]
Target Milestone: Future → mozilla0.9
moving to mozilla0.8 milestone.
Target Milestone: mozilla0.9 → mozilla0.8
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9
marking nsbeta1-. We are going to focus on thread pane performance rather than this.
Keywords: nsbeta1 → nsbeta1-
Whiteboard: [dogfood-][nsbeta1+] → [dogfood-][nsbeta1+ 1/28]
Target Milestone: mozilla0.9 → Future
*** Bug 68892 has been marked as a duplicate of this bug. ***
fixed.  (for my patient pal leaf, who has waited for so long.)

back to my 0.9 bug list...
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
yeeeaahh!! Thanks seth, I appreciate it too..
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I hate to do this to you, but there's no accelerator for this, which makes it
basically useless.. reopening to get an accelerator.
fix in hand for the accelerator ("accelerator shift a"). 

I'll get that in today.
Status: REOPENED → ASSIGNED
i saw this checked in on the trunk.. seth, mark this FIXED?
ugh. i didn't read alecf's comment, forget my last comment.
accelerator checked in.  marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Linux (2001-04-04-05 trunk)
Win32 (2001-04-04-06 trunk)
MAc (2001-04-04-04 trunk)
verified it works.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.