Closed Bug 44572 Opened 24 years ago Closed 23 years ago

Delete doesn't enable in some cases using Next Unread.


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



(Not tracked)



(Reporter: laurel, Assigned: sspitzer)



(Whiteboard: [cut 8/28] relnote-user)

Using july 5 commercial build
Seen using NT 4.0 and linux rh6.0
Haven't tried mac yet

Delete is often not enabling when landing on a message via Next Unread after
having switched folders or when first launching mail, logging into mail account
and using Next to read new messages in inbox.

1.  Launch IMAP profile to mail which you know will have some new messages in
the inbox. 
2.  Select INBOX if not already autoselected and provide proper login password.
3.  Let folder finish loading, notice the Delete button is disabled.
4.  Click Next (Unread) button. Lands you on the next unread message, message
loads in message pane.  Notice the delete button is still disabled, can't use it
to delete.  The button will stay disabled until you manually select a message in
the thread pane or may clear if switching folders.

Note:  Same thing occurs frequently when switching among folders and using Next
within a newly selected folder.

Result:  Delete button stays disabled until you select thread ("manually") in
thread pane.
QA Contact: lchiang → laurel
I see this too. Moving to M18 and nominating for beta3.
Keywords: nsbeta3
Target Milestone: --- → M18
Keywords: relnote2
Keywords: mail2
+ per mail triage
Whiteboard: [nsbeta3+]
reassigning to varada.  This is actually a focus bug.  It's not enabling because
focus is on the folder pane and the inbox is selected. If you were on another
folder and hit delete then it would try to delete the folder. We need to get
focus on the thread pane.
Assignee: putterman → varada
adding myself to cc list.
second pass: - per mail triage
Whiteboard: [nsbeta3+] → [nsbeta3-][cut 8/28]
Keywords: relnote3, relnoteRTM
removing mail2 keyword.
Keywords: mail2
Whiteboard: [nsbeta3-][cut 8/28] → [nsbeta3-][cut 8/28] relnote-user
QA Contact: laurel → sheelar
Re-assigning bug to sspitzer as per putterman.
Assignee: varada → sspitzer
clearing milestone, m17 and m18 are meaningless now.  these need to be triages
along with the rest.
Target Milestone: M18 → ---
Whiteboard: [nsbeta3-][cut 8/28] relnote-user → [cut 8/28] relnote-user
This works fine for me in 030608 mozilla linux build.  I followed laurel's steps
exactly and Delete was enabled.  Laurel, are you still seeing this?
Deleting is horrible still.  I tried to delete 156 mail docs from my inbox.  It
took 4 attempts.  The screen flickered and flashed and many docs. were still
left in my inbox and I had to do it over and over again until they were gone. 
Main is our most important use of this application and I hope it is fixed before
the next beta.
Asa: I see this, and can reproduce it with the original steps 100%. I was going
to file a bug on it if I hadn't found this. And indeed, it is a focus issue.
When the box is selected (e.g. by clicking on it), and you then press N, along
with the message header mechanically being selected and the message displayed if
the message pane is open, focus should shift to the message pane (IMO) or
alternatively the header pane. This should enable the delete button /
accelerator key., I believe what you are seeing is a different bug which
was fixed a while back (I haven't seen it for a long time, that is).
I don't think it's completely a focus problem. Note that the thread pane *does*
get the focus after clicking on a mailbox (which makes it sucky to navigate the
folder hierachy by keyboard - maybe that should be filed as a bug).

The bug is still reproducable, but only if you use keyboard navigation -
pressing "N" or "F" after selecting a folder will do it. The problem does not
occur if you click on the "Next" button. Interestingly, you can still delete the
message using the keyboard, even though the Delete button is disabled.

Given it's only a problem when using the keyboard, shouldn't this have the
keyword "access"?
I'll look into the bug further.
The problem with this is nsMsgDBView::GetCommandStatus() is incorrectly
returning false when called by DefaultController.isCommandEnabled() in
mail3PaneWindowCommands.js (and possibly by others)

Interestingly, fixing bug 97134 fixes this, so either something is broken in
nsUInt32Array or nsMsgDBView::GetSelectedIndices().

I'll look further into precisely which of those two are broken.
Adding myself to the CC list, aplogies for the spam.
Depends on: 97421
The root cause of the problem is the outliner's over-anxious key event handlers.
Pressing a key causes the thread outliner to select a non-existing row. This
error the propagates up to nsMsgDBView::GetCommandStatus() via

Fixing the outliner's handler (bug 97421) fixes this bug.
No longer depends on: 97421
This may be a related problem. The following was tested under Mac/0.9.3 and

1. Select an IMAP folder with one and only one message inside
2. Observe focus is now on message pane
3. Select All using the keyboard (Cmd- or Ctrl-a)
4. Observe that the message is selected but the Delete button is not enabled

This only occurs if there is one and only one message in the folder. Deselecting
the selected message and reselecting all using the keyboard causes the Delete
button to enable.

Choosing Select All from the menu does always cause the Delete button to enable.

What do you think? Is this part of this bug, or should I open a new one?

(Propose that this bug is All/All.)
It looks like the same problem - any way you can cause a single message to be
selected after selecting a folder using keystrokes will reproduce this behaviour.
Blocked by bug 97421
Depends on: 97421
This has been fixed in bug 84260.

*** Bug 113937 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 84260 ***
Closed: 23 years ago
Resolution: --- → DUPLICATE
this is a dup of a fixed bug. removing item for this bug from release notes.
verified as dup.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.