[Pidgin] #10462: Custom URLs no longer function
Pidgin
trac at pidgin.im
Wed Oct 7 17:50:28 EDT 2009
#10462: Custom URLs no longer function
--------------------------+-------------------------------------------------
Reporter: jcmoore | Owner: rekkanoryo
Type: defect | Status: new
Component: unclassified | Version: 2.6.2
Keywords: URI handler |
--------------------------+-------------------------------------------------
As of Pidgin 2.6.2, Pidgin seems to no longer pass URLs for certain
protocols off to Windows for handling. In older Pidgin versions (at least
in 2.5.8), I was able to have a URI like myprotocol://some.cool.resource
and Pidgin would pass this URL off to Windows for handling. Since this
URL protocol had been registered with Windows, the link opened in the
specified program as per the instructions here: http://msdn.microsoft.com
/en-us/library/aa767914%28VS.85%29.aspx .
As of Pidgin 2.6.2, whenever I receive a message containing a link using a
custom protocol, Pidgin recognizes the fact that the URI is a link as it
formats it as an href (pointer turns to a hand when mouse is moved over
link) but when I try to click on the link, the registered program does not
open to handle the link.
If I try to right click on the link I receive a context menu stating "No
actions available". This is contrast to what happens when I right click
on an http:// style URL, I get a context menu with the options: "Open
Link" and "Copy Link Location".
Additionally, it appears that this is also non-functioning with xmpp:
style URIs, last discussed here: http://developer.pidgin.im/ticket/2326 .
Was the URI handling code touched in 2.6.0 as indicated in this ticket?
Could something have inadvertently changed to cause this behavior?
--
Ticket URL: <http://developer.pidgin.im/ticket/10462>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list