Closed Bug 17085 Opened 25 years ago Closed 25 years ago

[regression] Mailto links are broken

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 14928

People

(Reporter: pmock, Assigned: mscott)

Details

Build Date & Platform Bug Found:
 Win32 commercial seamonkey build 1999-10-22-09-m11 installed on P166 Win98
 MacOS mozilla seamonkey build 1999-10-22-08-m11 installed on G3/400 OS 8.5.1
 Linux commercial seamonkey build 1999-10-22-08-m11 installed on P200 RedHat 6.1

Overview Description:
 Mailto links are broken in messenger and the browser.  When you click on a
link, nothing happens.  No compose window appears.

Steps to Reproduce:
Messenger
1) In Communicator 4.7, create a mail message with a mailto link.
   such as 'mailto:pmock@netscape.com'
2) Send mail message to yourself
3) In Seamonkey, retrieve the message
4) Click on the link
   nothing happens

Browser
1) In Communicator 4.7, create a web page with a mailto link
2) Save the html
3) In Seamonkey, open the html you created in 4.7
4) Click on the link
   nothing happens

Actual Results:
 The mail compose window does not appear.

Expected Results:
 The mail compose window should appear.  The address pane should have the user
email address already filled in.

Additional Builds and Platforms Tested On:
I am marking this a reggression because mailto links were working according to
bug 10892 that I was trying to verify.

Additional Information:
The problem does not occur on the 4.7 RTM builds of Win32, Linux, and Mac.
QA Contact: lchiang → pmock
changing qa contact to myself.
I think mscott has a bug on this already.  Under URL dispatching?
Blocks: 10892
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Yeah this stuff will get all fixed up again when url dispatching lands. Marking
as a dup.


*** This bug has been marked as a duplicate of 14928 ***
Status: RESOLVED → VERIFIED
Verified as duplicate
No longer blocks: 10892
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.