Closed
Bug 249037
Opened 21 years ago
Closed 19 years ago
can not multiselect groups or articles to set them all watch/ignore
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: uspam, Unassigned)
References
Details
User-Agent: Opera/7.23 (X11; Linux i686; U) [de]
Build Identifier: Mozilla Thunderbird 0.5 (20040306)
I want to set more than one articles/threads watch/ignore in only one step.
I mutliselect all needes threads and then press 'K'.
But it does not work, because If I multiselect threads the watch/ignore
menupoint is disabled.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•20 years ago
|
||
*** Bug 282992 has been marked as a duplicate of this bug. ***
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Comment 4•13 years ago
|
||
works
Assignee: mscott → nobody
Severity: major → normal
QA Contact: front-end
Resolution: EXPIRED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•