User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20100107 Fedora/3.5.6-1.fc12 Firefox/3.5.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20091209 Fedora/3.0-4.fc12 Lightning/1.0b2pre Thunderbird/3.0 When clicking on the first message in collapsed thread, I see only the content of that one message. There is no thread summary. The account uses POP and all messages are downloaded and stored locally. I have rebuilt the indices for the folders. Reproducible: Always Steps to Reproduce: 1. Collapse thread 2. Click on first message 3. ? Actual Results: see content of first message Expected Results: see summary of all messages in the thread
does this happen on all threads or on a specific one ? This feature is based on the global index, it needs to be active and the messages need to have been indexed bu it (use the glodaquilla extension to see this information), can you check both of these points ? While checking can you look in tools -> Error console for errors when this happens ? Does this happens in -safe-mode ?
1) global indexing is enabled and active 2) it happens on all threads in all folders. 3) the glodaquilla extension requires some sort of sandbox account 4) there are a lot of "document is null" messages in the error console Error: document is null Source File: chrome://messenger/content/FilterListDialog.js Line: 54 5) Is there a way to disable or enable the feature? May I disabled it during one of the betas.
(In reply to comment #2) > 5) Is there a way to disable or enable the feature? May I disabled it during > one of the betas. yes there is , I think it's mail.operate_on_msgs_in_collapsed_threads that needs to be set to true.
Thank you. Silly me, I was searching on "summary". <smile> I probably turned it off when it was broken in one of the early betas.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
WFM , this is not a code FIX :-)
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.