Closed
Bug 858951
Opened 11 years ago
Closed 11 years ago
Seamonkey Email component does not display any content at all
Categories
(SeaMonkey :: MailNews: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 858014
People
(Reporter: masinick, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20a1 Build ID: 20130406003001 Steps to reproduce: Opened the Seamonkey Mail component. Expected to see a list of folders, messages, and content. Actual results: The visible user interface to Seamonkey Mail, as of the Friday and Saturday builds, and also the 0406 Tinderbox build, is completely devoid of any visible content. I cannot see any messages, folders, or information whatsoever. The browser component, however, appears to be working normally. Curiously, the Mail component does seem to be recognizing content; it's just not viewable. Switching over to Iceape or an earlier instance of Nightly, then messages are viewable as expected.. Expected results: I consider this a Mail display regression. The folders, messages, and content should be viewable. I will check back to see if I can isolate which exact nightly build day this issue was introduced; I think it was either the Thursday or Friday nightly build.
User agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20a1 Build identifier: 20130403003001 is the latest Nightly Build that I've been able to get properly working; I have reverted to using it; builds from 04-04, 04-05, 04-06, and the latest Tinderbox build that I've tried all exhibit the behavior of not displaying any Mail content; no folders, no Email messages, though the messages are still present; nothing has been removed; this appears to be a display issue, because when I revert versions, it does work, though I do seem to have to utilize the repair folder features in the Properties section to get everything 100% as it should be.
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•