Bug 397429 - Firefox doesn't offer konversation when clicking irc-links
Summary: Firefox doesn't offer konversation when clicking irc-links
Status: RESOLVED DUPLICATE of bug 113512
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Firefox (show other bugs)
Version: RC 1
Hardware: All Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-05 11:32 UTC by Martin Schlander
Modified: 2008-06-06 14:56 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screenshot of clicking irc-link in FF (111.80 KB, image/png)
2008-06-05 11:32 UTC, Martin Schlander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schlander 2008-06-05 11:32:25 UTC
Created attachment 220403 [details]
Screenshot of clicking irc-link in FF

Clicking an irc-link in Firefox (in KDE 4.0) it asks whether to use Xchat or "select other app". Clicking "Select other app" opens the Gtk file dialog in which very few people will be able to find the konversation executable.

This is a major problem. For example the irc-section of help.opensuse.org will be useless for Firefox+KDE users. There are probably substantially more openSUSE users with Firefox+KDE than Firefox+GNOME.

I suggest to make FF offer both Konversation and Xchat for irc links by default. If it's only possible to have one app by default it should be konversation.

Attaching screenshot.
Comment 1 Wolfgang Rosenauer 2008-06-05 11:48:34 UTC
Unfortunately there is no way to modify that from Firefox easily.
Firefox uses gconf to find a protocol handler for IRC and gconf has xchat as default handler. There is currently no way to change that w/o implementing new features within Firefox.
We have quite some bugs about missing KDE integration of Firefox.
Comment 2 JP Rosevear 2008-06-06 14:56:39 UTC

*** This bug has been marked as a duplicate of bug 113512 ***