User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Thunderbird version 1.0RC1 (20041201) I often go to my spam folder to finetune/test message filters (not the junk filter), and have to select that folder in the "Run selected filter(s) on:" dropdown. It would be nice if that folder (the currently opened folder) was already selected. Reproducible: Always Steps to Reproduce: Actual Results: go to any other folder than the Inbox. Open "Tools" -> "Message Filters". When you want to test a filter on the current folder, you first have to select it in the dropdown. Expected Results: Pre-select the currently opened folder.
Actually, this RFE still holds. Any chance on confirming?
Preselect current folder used to be implemented in TB2; it have been dropped from TB3. Please re-introduce it !!! I want this feature BACK.
(In reply to comment #3) > Preselect current folder used to be implemented in TB2; it have been dropped > from TB3. This feature isn't present in TB2, unless you had an addon that did this.
For the last years, I don't know for how long exactly, thunderbird has pre-selected the folder automatically for me, as far as I understood it selected the folder the currently selected mail is in. This worked pretty well and I always never had to change the selection. Yesterday I updated from thunderbird 38.5.0 to 38.7.0 and got the behaviour described here: The field is empty and I _have_ to select anything before being able to run the filter(s). This might seem to be a minute detail, but it really is one additional click multiple times a day for no appearent reason. I think before I want to second this 'bug', I want to know what the actual implementation is/does, what of it is configurable and what the logic behind not selecting anything is.
You're probably doing something different than you used to, or are talking about a different bug, since this bug was filed 12 years ago, long before TB version 38.x was even a twinkle in the developer's eyes.
You need to log in before you can comment on or make changes to this bug.