Closed Bug 669872 Opened 15 years ago Closed 14 years ago

Open eml file: Reply button present but not functional

Categories

(SeaMonkey :: MailNews: Message Display, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: me, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110623 Firefox/7.0a1 SeaMonkey/2.4a1 Build ID: 20110623003152 Steps to reproduce: Started Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110623 Firefox/7.0a1 SeaMonkey/2.4a1 Receive mail from pop server Save one mail as .eml file Delete mail, empty trash Open file using "Open" in message overview (where inbox is visible) New window displaying message appeared, reply/reply-all buttons available Click on "reply" PS: Same result with reply-all, copy message to folder (inbox/trash) Actual results: Nothing Expected results: New window with message composer to create new reply.
Tried again to see, if related to bug 669894 (SEGV in open). After 2 more fails, reply worked, so not 100% reproducible
Open the error console. Tools->Web Development->Error Console Clear all items in the console. Do your Steps to reproduce. Do any error messages appear in the Error Console?
Reproduced with Mozilla/5.0 (X11; Linux i686; rv:8.0a1) Gecko/20110706 Firefox/8.0a1 SeaMonkey/2.5a1 Just 1 message in console: Error: loadedFolder is null Source File: chrome://messenger/content/mailWindowOverlay.js Line: 1126
Works for me: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110708 SeaMonkey/2.5a1 and: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.2pre) Gecko/20110520 Firefox/4.0.2pre SeaMonkey/2.1.1pre Do you have any mail extensions installed that might interfere? Can you try SeaMonkey safe-mode? Help->Restart with Addons disabled.
Restart with addons did not fix it, but new version seems to have fixed it: At least since Seamonkey 2.7a1.en-US.linux-i686 nightly 20111015 it is working
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.