Closed
Bug 420273
Opened 18 years ago
Closed 17 years ago
Ignore thread selects message in next thread
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dave, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.12) Gecko/20080203 SUSE/2.0.0.12-2.1 Firefox/2.0.0.12
Build Identifier: version 2.0.0.12 (20080226)
Newsgroups. Using threads with unread view. All threads collapsed.
I select a thread (I normally use cursor keys & read down) and hit K.
This usually expands another thread - which is usually the following one. Sometimes it expands a later one (eg if you un-ignore and re-ignore). If there's only one post in the following thread it just selects it.
Reproducible: Sometimes
Steps to Reproduce:
1.Select threads with unread view
2.Select a newsgoup
3.Collapse all threads if they're not already
4.Select a thread. Choose one with >1 post where the next one also has >1 post
5.Hit K
Actual Results:
Expands another thread -usually the following one.
If you repeat the process several times (collapse the thread, then re-select the ignored thread and press K again) it usually expands later threads
Expected Results:
Mark thread ignored and leave it selected
Also happens in Windows 2.0.0.12.
This is the designed behavior. Also in 3.0a2. I can assume is somehow related to same behavior when del on a mail msg. Which moves to next msg in the same manner.
For that, those that do not like it use Unselect Message extension
https://addons.mozilla.org/en-US/thunderbird/addon/1397
Not sure if works for the news case here, but the principle is same.
OS: Linux → All
Hardware: PC → All
Comment 2•17 years ago
|
||
from a workflow POV I think this should be wontfix.
Summary: Ignore thread expands a later thread → Ignore thread selects message in next thread
Comment 3•17 years ago
|
||
yes, this is as designed.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•