My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 20696: External protocol handlers not implemented (e.g. mailto:)
7 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  mdm@chromium.org
Closed:  Sep 2009

Restricted
  • Only users with Commit permission may comment.


Sign in to add a comment
 
Project Member Reported by evan@chromium.org, Aug 31, 2009
What steps will reproduce the problem?
1. Click a mailto: link.
2. 10064:10064:1295074290997:ERROR:/build/buildd/chromium- 
browser-3.0.194.0~svn20090711r20448/build-tree/src/chrome/browser/ 
external_protocol_handler.cc(167)] Not implemented reached in static 
void ExternalProtocolHandler::LaunchUrl(const GURL&, int, int) 
Aug 31, 2009
#1 est...@chromium.org
(No comment was entered for this change.)
Cc: m...@chromium.org
Sep 1, 2009
#2 bugdroid1@gmail.com
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=25100 

------------------------------------------------------------------------
r25100 | mdm@chromium.org | 2009-09-01 15:32:26 -0700 (Tue, 01 Sep 2009) | 5 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/external_protocol_handler.cc?r1=25100&r2=25099
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/platform_util.h?r1=25100&r2=25099
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/platform_util_linux.cc?r1=25100&r2=25099
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/platform_util_mac.mm?r1=25100&r2=25099
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/platform_util_win.cc?r1=25100&r2=25099

Linux: handle external protocols, e.g. mailto: links.
BUG=20696
TEST=click a mailto: link, it should open your default MUA

Review URL: http://codereview.chromium.org/177040
------------------------------------------------------------------------

Sep 1, 2009
#3 mdm@chromium.org
Chromium should now use xdg-open to handle external protocols. This works for mailto: 
but not, e.g., apturl (https://code.google.com/p/chromium/issues/detail?id=18113). But 
mailto: is probably the most important...
Sep 16, 2009
#4 pkasting@chromium.org
So, is this bug fixed or not?
Sep 16, 2009
#5 evan@chromium.org
Why doesn't xdg-open support apturl?
Sep 16, 2009
#6 mdm@chromium.org
This should be fixed. Also it turns out that apt: URLs do actually work, it's just 
that system support for them is often broken by default (see http://crbug.com/18113 
for how to configure it correctly). Also see http://crbug.com/21934 if you find that 
it's not doing what you expect; xdg-open doesn't handle unusual desktop environments 
very well.
Status: Fixed
Owner: m...@chromium.org
Cc: -m...@chromium.org
Mar 9, 2010
#7 bausparf...@googlemail.com
I would love to have a settings page for that, so that you can choose an action fr 
some protocols. I'm here on Ubuntu Karmic using chromium. I run the famous "Spotify" 
in wine, and want to have its playlist links from the web opened inside the running 
spotify. Therefore it is required, that chromium calls a little script and gives the 
URL of the Playlist as an argument. That action works without truble in Firefox, cause 
there is the possibility to define wn protocol handlers in "about:config". Any Ideas 
how this can be done with chromium?
Mar 10, 2010
#8 mdm@chromium.org
It should be using xdg-open, which will use your desktop environment's settings to figure out what to do. If you 
are using GNOME, you should be able to configure GNOME to know how to handle those protocols and then it will 
work. Likewise, if you are using KDE, you would use KDE's protocol handler configuration to set it up. (In general 
we try to use the desktop environment's settings for as many things as possible, to avoid duplicating 
configuration data.)
Mar 10, 2010
#9 bausparf...@googlemail.com
I'm on KDE. But I really don't know how to get klauncher recognise that specific 
Protocol. It works from inside Firefox by editing the about:config page. But that does 
not affect the rest of the KDE Protocol handlers. I found xdg-mime to determine a 
filetype of a specific file and use xdg-mime to set the standard action for that. But 
that does not work with a protocol.
Oct 11, 2012
#10 bugdroid1@chromium.org
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Labels: Restrict-AddIssueComment-Commit
Sign in to add a comment

Powered by Google Project Hosting