After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 116121 - No mail handler error should offer to help
No mail handler error should offer to help
Status: RESOLVED WONTFIX
Product: epiphany
Classification: Core
Component: General
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Marco Pesenti Gritti
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2003-06-27 14:46 UTC by spark
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description spark 2003-06-27 14:46:12 UTC
When you have no mail handler set up and go File -> Send To you get an
error saying you have no handler set up. This error dialog should have a
button offering to open the relevent configuration tool.
Comment 1 Dave Bordoley [Not Reading Bug Mail] 2003-06-29 14:08:56 UTC
Only problem is that the filetypes capplet doesn't accept parameters
to change the settings of a protocol just mimetypes. Another option is
to automatically set the handler to evolution, although i'm not sure
it would handle it correctly.
Comment 2 spark 2003-06-29 14:18:13 UTC
Maybe just opening the filetypes capplet would be ok as a compromise?
Comment 3 Christian Persch 2003-12-11 11:00:46 UTC
The nohandler dialogue comes from mozilla, there's nothing we can do
with it I think.
Comment 4 spark 2003-12-11 23:48:52 UTC
How hard would it be to make Mozilla allow us to use our own dialog 
here?
Comment 5 Marco Pesenti Gritti 2003-12-19 19:26:51 UTC
very hard (design a class for it). I vote WONTFIX.
Comment 6 Christian Persch 2003-12-30 18:37:18 UTC
The dialogue is displayed from
http://lxr.mozilla.org/seamonkey/source/docshell/base/nsDocShell.cpp#2484
(nsDocShell::DisplayLoadError) via the prompt service; so we'd need to
re-implement it.

Our only option is using browser.xul.error_pages.enabled. That'll
display the error as a web page instead of presenting a dialogue. But
currently it 1) uses XUL, and 2) isn't over-rideable for embedders, so
we can't provide our own page with hints on how to set the handler up.

WONTFIX / NOTGNOME