Closed Bug 430181 Opened 17 years ago Closed 13 years ago

Deleting Tagged Mail Message in "Grouped by Sort" display creates additional messages in display window

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hwsw, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080325 Fedora/2.0.0.13-1.fc8 Firefox/2.0.0.13 pango-text Build Identifier: version 3.0a1pre (2008042103) I have started to use tags extensively by creating message filters to tag incoming mail. My messages are sorted by date and are displayed using "Grouped by Sort" like this: - Messages Today - Message One - Message Two - Message Three - Message Four If I delete the "Message Three" all of the messages from the Grouped By header up to the deleted message are displayed again with the duplicates being collapsed. This is the display after the deletion of "Message Three": - Messages Today - Message One - Message Two + Message One - Message Four and after expanding the message tree: - Messages Today - Message One - Message Two + Message One - Message One - Message Two - Message Four This behavior can be seen on Linux (Fedora 8) as well as Windows XP. I have tested the latest build for Windows (using an empty profile) and still see this. The problem only shows up when messages are displayed using the Grouped By style. Turning Grouped By off displays all messages correctly when deleting messages. Reproducible: Sometimes Steps to Reproduce: I was able to reproduce this most reliably (but not always) in the following two ways: 1. Start Thunderbird (there are new, unread messages available) 2. Highlight a message 3. Delete the message In order to "reset" the display select a different folder and then select the inbox folder again. Now, the messages display correctly and deleting additional messages will not cause this problem again for a while. It is possible that the problem will occur again after additional tagged messages have arrived. The second way to reproduce this behavior: 1. Create a message filter (Tools --> Message Filters...) 2. Create a filter to tag messages with the rule Tag Message -- Important 3. Once the filter has been created highlight it in the Message Filters window and click "Run Now" 4. Highlight a message that got tagged by the new rule 5. Delete the message by clicking the Delete icon Same as before, one can correct the display by switching between folders. Actual Results: I've created screenshots to display the result: A. After starting Thunderbird the message tagged purple is about to be deleted: http://kepler.englisch.us/~volker/TB/Bug_A1.jpg B. After deleting a message the display shows the first message of the "Today" group replaced by the deleted message. http://kepler.englisch.us/~volker/TB/Bug_A2.jpg C. When clicking on the +-sign one can see that all messages from the top of the "Today" group up to the purple message have been duplicated. http://kepler.englisch.us/~volker/TB/Bug_A3.jpg Expected Results: A deleted message should be gone to Nirvana. Deleted messages should be gone and not replaced.
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008050715 Lightning/0.6a1 Thunderbird/3.0a1 ID:2008050715 not able to reproduce in this ver (well, maybe not trying hard enough ..) Could you try a newer build, alpha1 or alpha2pre?
Version: unspecified → Trunk
(In reply to comment #1) > not able to reproduce in this ver (well, maybe not trying hard enough ..) It doesn't surprise me because I only seem to encounter this behavior for one particular tag/email. The messages for which this is happening are tagged using the rule: Subject Begins with [FreecycleOlneyMD] I hope the problem hasn't anything to do with the color I picked to highlight the messages. :-) I will download a newer build, try again and report back.
I tried a nightly build version 3.0a2pre (2008060603) and can still see the reported problem.
(In reply to comment #2) > It doesn't surprise me because I only seem to encounter this behavior for one > particular tag/email. > The messages for which this is happening are tagged using the rule: > Subject Begins with [FreecycleOlneyMD] What is tag identifier of the particular tag? ( xyz part of user_pref("mailnews.tags.xyz.tag", "Text string for this tag"); ) ( == text string written in X-Mozilla-Keys: header when local mail folder. ) When xyz is substring of other tag(i.e. xyzp, xyzpq, xyzpqr etc. are also defined), several issues can occur. See Bug 4333175 Comment #15 for an already reported severe problem(loop, thus freeze for user).
> What is tag identifier of the particular tag? It is ("mailnews.tags.$label5.tag", "Lists") I don't have any tag labels that are substrings of other tags but I do have a string value that is a substring of a tag ("mailnews.tags.newslists", "NewsInfo") Could this be related?
(In reply to comment #5) > ("mailnews.tags.newslists", "NewsInfo") "mailnews.tags.newslists"? If yes, it possibly has relation to problem. If "mailnews.tags.newslists.tag", problem shouldn't be produced by this tag, if tag name related issue. "Lists" and "NewsInfo" is simply a label(displayed in UI for tag choice) for tag named $label5 and newslists(used in X-Mozilla-Keys:, filter rule in msgFilterRules.dat) respectively. I can't think combination of ("mailnews.tags.aaa.tag","zzz") & ("mailnews.tags.zzz.tag","aaa") produces problem, it'll surely produce my confusion though.
Volker, do you still see ths problem when using version 3 or version 5?
Severity: normal → minor
Component: Mail Window Front End → Folder and Message Lists
QA Contact: front-end → folders-message-lists
Whiteboard: [closeme 2011-08-21]
No. I'm currently using TB 3.1.11 on Ubuntu 10.10 and TB 5 on Windows. I don't remember exactly when this problem was resolved, probably around the release of version 3.1. I believe this issue can be closed.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2011-08-21]
You need to log in before you can comment on or make changes to this bug.