User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:22.214.171.124) Gecko/20070312 Firefox/126.96.36.199 Build Identifier: 20070326 When I create a custom view to exclude certain tags, messages with one of the default tags are still displayed. I can however exclude tags I created. Reproducible: Always Steps to Reproduce: 1. Create a custom view: Tags - isn't - Personal 2. Select the created view Actual Results: 3. Messages tagged personal are still displayed Expected Results: Messages tagged personal should have been excluded from the view.
WFM on 2.0/linux. Did the message have other tags too?
I could imagine two cases here: 1. a message could have an unmigrated label value -> this should go away at the latest when toggling the respective tag 2. the message arrived in this folder _after_ the view was selected, e.g. you're in an inbox -> feature, not a bug Which version of TB are you using? Does reapplying the view help?
(In reply to comment #1) > WFM on 2.0/linux. > > Did the message have other tags too? No, Personal was the only tag. (In reply to comment #2) > I could imagine two cases here: > 1. a message could have an unmigrated label value > -> this should go away at the latest when toggling the respective tag This didn't work. I actually deleted the Personal tag, recreated it and retagged the messages. Still the same problem. > 2. the message arrived in this folder _after_ the view was selected, e.g. > you're in an inbox > -> feature, not a bug This was not the case and reapplying the view doesn't make it disappear. > Which version of TB are you using? version 188.8.131.52 (20070326)
Peter, does this issue still occur in the latest supported 184.108.40.206 / trunk nightlies?
Hi Gary, I have recreated the issue following the steps in my original message. TB 220.127.116.11 still shows the excluded messages. Peter
Ah, ok i see this now. Confirming on linux/trunk (imap account). Tags "doesn't contain" work as expected though.
bug 577819 comment 4 points out that this problem might be bigger than just default tags, there's something wrong with the tags search UI and/or behaviour.
I can't confirm this bug. It works for me. It seems that it is solved.