Closed
Bug 149288
Opened 22 years ago
Closed 22 years ago
Crash after cancelling initial MailNews account setup
Categories
(SeaMonkey :: MailNews: Account Configuration, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 144908
People
(Reporter: mail2jbm, Assigned: racham)
References
()
Details
(Keywords: crash, stackwanted)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0rc2) Gecko/20020510 BuildID: 2002051005 I've only used Mozilla for browsing, not for mail. I clicked on a mailto: link, and the compose window came up along with the new account setup window. I clicked "cancel", and the "are you sure?" window came up, (not called that, but something like that). I clicked "exit" in the "are you sure?" window, another window came up very quickly (I couldn't tell what it was) then Mozilla died and a window came up saying it had died. It would probably happen with any mailto: link, but the one I found it on was at http://www.clickteam.com, from there highlight the "resources" menu iteam at the top, and select the "about clickteam" option. On the right side of the screen, under the "contact us" heading, a short way down is a link to "support". This is the link where I found the problem. Reproducible: Always Steps to Reproduce: 1.Follow instructions in Description section. 2. 3. Actual Results: Same result. Expected Results: Cancelled out of mail setup without crashing Mozilla.
Simplifying Summary.
Severity: major → critical
Keywords: crash
Summary: crash if click on mailto link when haven't set up mail before, and cancel out of mail setup → Crash after cancelling initial MailNews account setup
Jeff, that build's a bit out of date at this point. Please retest using a current build.
Comment 4•22 years ago
|
||
This is a duplicate of bug 144908.
Comment 5•22 years ago
|
||
*** This bug has been marked as a duplicate of 144908 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•