Closed
Bug 265746
Opened 20 years ago
Closed 20 years ago
"Mark as Junk Mail" deselects selected messages
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: db48x, Assigned: mscott)
Details
I do not have Thunderbird set to automatically move junk mail to the junk folder as I'm still training it. Whenever I mark a message as junk, thunderbird clears the selection, which means I then have to reselect the junk mail in order to move it to the junk folder manually. The selection should instead be preserved.
Comment 1•20 years ago
|
||
Is the selection one or more than one message? Which technique are you using to mark it as junk -- the toolbar Junk button, the toolbar Mark button, the 'J' hotkey, the message context menu, the top level Message menu (all of which should behave the same), or clicking in the Junk column? If you're clicking in the column, are you marking the selected message junk, or marking some other message outside of the selection? You say that TB is not "set to automatically move junk mail to the junk folder" -- there are actually two checkboxes to control that, one for messages detected as junk and one for messages manually marked as junk. Do you have both checkboxes cleared?
Comment 2•20 years ago
|
||
version 0.8 (20041025) Windows 2000 Ok, I'm having the same issue, slightly different circumstances. I have the mail that I manually mark as junk moved to the junk folder (in same account folder). When I have 1 message selected and and mark it as junk it does not select the next message in the folder. This happens with all methods: 'j' click on toolbar button,right click on message->mark->as Junk,click in junk column, top level menu item. If there is more than 1 message highlighted, then it does select the next message with all the methods listed above.
Comment 3•20 years ago
|
||
Daniel Brooks, I still am trying to figure out your problem; please respond to comment 1. Chris Martin, your bug sounds more like bug 266066. It's possible this bug is the same or closely related, but I don't have a handle on it yet.
Comment 4•20 years ago
|
||
No response from reporter; =>WFM
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•