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 452637 - Wrong behaviour on mailto: links
Wrong behaviour on mailto: links
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-30 19:59 UTC by Behnam Esfahbod
Modified: 2008-06-26 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Behnam Esfahbod 2007-06-30 19:59:00 UTC 
On links like mailto:name@example.com, there would be two links:

1- The whole URI, "mailto:name@example.com", which has context-menu items "Open Link" and "Copy Link Address".

2- The TLD part, ".com", which has context-menu items "Send Mail To..." and "Copy E-mail Address".

This is wrong.

The simple fix is to make sure the whole address works for the second link, and the email address, plus the mailto: schema, behaves like a simple link.

OTOH the best fix would be to make it something like Thunderbird's, which have more options (all for context menu items, with better texts) on the whole email address linking (with or w/o the mailto schema).
Comment 1 Chris Jones 2008-02-21 07:57:54 UTC 
I can confirm this too.
If it helps, I'm running Ubuntu Hardy, but I saw this on Gutsy too.

It's quite specific too, various other forms of email address won't trigger this.
Comment 2 Maxim Ermilov 2008-06-26 14:35:08 UTC 
This bug has in 2.22.1 version. But 2.23.4-svn version has not this bug.
Comment 3 Chris Jones 2008-06-26 15:20:29 UTC 
http://bazaar.launchpad.net/~gnome-terminator/terminator/trunk/revision/373 shows how we fixed this in Terminator, which was previously using the same match that gnome-terminal uses.
Comment 4 Christian Persch 2008-06-26 23:05:08 UTC 
Right, this is fixed in svn trunk using vte svn trunk.