[Pidgin] #10462: Custom URLs no longer function

[Pidgin]

#10462: Custom URLs no longer function
-------------------------+--------------------------------------------------
 Reporter:  jcmoore      |        Owner:  datallah       
     Type:  defect       |       Status:  new            
Milestone:               |    Component:  winpidgin (gtk)
  Version:  2.6.2        |   Resolution:                 
 Keywords:  URI handler  |  
-------------------------+--------------------------------------------------
Changes (by datallah):

  * owner:  => datallah
  * component:  pidgin (gtk) => winpidgin (gtk)


Comment:

 Replying to [comment:2 jcmoore]:
 > I would also agree that it's preferred to pass URIs to their registered
 Windows handlers instead of passing them to the browser and having it call
 the Windows handler as that seemed kind of like an unintended side effect
 anyway.

 Actually, I don't think that is a good idea to pass stuff to arbitrary
 handlers.  There have been a whole host of security issues (like
 [https://bugzilla.mozilla.org/show_bug.cgi?id=389106 this]) that we avoid
 responsibility for by only sending stuff to the http open handler - that
 is why we did it in the first place.

 > I would suggest that we enumerate the Windows URI handlers before the
 plugin URI handlers and if there is a plugin that happens to handle the
 same URI type as a registered Windows URI type, the plugin's URI handling
 capability will override the Windows handler and have precedence over the
 base Windows URI handler.

 I have a patch that I'm testing that does this in the same way that we
 register handlers for stuff that GNOME knows about (still sending the
 actual URL to the http open handler).

 > As an additional step, if a string resembling a URI is encountered but
 which has no handler, either through Windows or a plugin, then don't treat
 it as an HREF.  I find it somewhat misleading that Pidgin treats anything
 resembling protocol:// as an HREF even if there is no URI handler
 registered to handle the protocol specified.  If there is no handler the
 string should appear no different than regular text; this could be open to
 debate.

 This is a different (non-windows specific) issue, please file a separate
 enhancement ticket for it.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/10462#comment:3>
Pidgin <http://pidgin.im>
Pidgin