Closed
Bug 147414
Opened 23 years ago
Closed 22 years ago
no error indication for mailto: form when MailNews not installed
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jmd, Assigned: adamlock)
References
()
Details
If I wasn't so used to Mozilla's poor handling of mailto: when MailNews isn't
installed, I would be quite puzzled why the form on the URL above doesn't submit.
Perhaps an error dialog would be useful?
Comment 1•23 years ago
|
||
This is a dup of the general "trying to load a url with an unknown scheme by
clicking or via form action does not give an error" bug....
Reporter | ||
Comment 2•23 years ago
|
||
I don't think so. Links show where they go at least when you hover. If not for
the hints on the page, it would be very unexpected why the form does not work.
mailto forms are rare (for good reason), and I think most definatly a differant
case then a href=foo:, since form actions require custom code for each action.
Comment 3•23 years ago
|
||
Wel.. seeing as we completely lack support for mailto: actions anyway at the
moment, there is in fact no custom code. Form submissions just ends up calling
nsWebShell::OnLinkClickSync with the eLinkVerb_Replace verb. This just calls
nsDocShell::InternalLoad, which is what any link click will do. Unfortunately,
InternalLoad has poor reporting of load failures....
Imo, trying to load a link "foo:bar" and submitting to "foo:bar" should return
the same error message (and the same code is involved in both cases).
uid is being phased out.
Assignee: mpt → adamlock
Component: User Interface Design → Embedding: Docshell
QA Contact: zach → adamlock
Boris, is this fixed by your checkin for that other bug?
Comment 6•22 years ago
|
||
It should be, yes. I have no mailnews-less build on hand to test with, however.
jmd, could you try tomorrow's build?
Depends on: 86486
Reporter | ||
Comment 7•22 years ago
|
||
Now I get: "mailto is not a registered protocol."
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•