540361 - Thunderbird fails to open http links from the e-mail body

Status: RESOLVED DUPLICATE of bug 216252

(Thunderbird :: General, defect, P2)

Description

[Yuri]

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.7) Gecko/20100114 Firefox/3.5.7
Build Identifier: version 2.0.0.23 opn FreeBSD-8.0

I click and nothing happens.

If no action is specified or specified application fails, message box should show up explaining what happened and telling user where to set related options.

Menu on right mouse click over the link should contain the item leading to setting up the http handler. Like "Set up http handler".

Reproducible: Always

Comment 1

[Ludovic Hirlimann [:Usul]]

Using gnome, KDE , just plain X ?

I think the handler can be set in the launch script

Comment 2

[Yuri]

Using KDE4.

The handler should be settable through TB menus since this has high user visibility.

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)
 
> The handler should be settable through TB menus since this has high user
> visibility.

Does it work if you do it in the launch script ?

Comment 4

[Yuri]

I don't know how to do this in the launch script.

But there is a configuration dialog about:config (Edit Menu->Preferences->Advanced Topic->General tab->Configuration Editor). There is value there: network.protocol-handler.app.http which is set to handler. This one works when set correctly.

When this value is set to nonexistent app the value gets silently ignored. This is the issue. If app doesn't exist GUI prompt should appear explaining what happened and asking user to change the value.

Comment 5

[Ludovic Hirlimann [:Usul]]

(In reply to comment #4)

> When this value is set to nonexistent app the value gets silently ignored. This
> is the issue. If app doesn't exist GUI prompt should appear explaining what
> happened and asking user to change the value.

We might have fixed that in TB3, ain't sure thought.

Using Gconf might help achieving what you want ..

Comment 6

[Yuri]

> Using Gconf might help achieving what you want ..
Thanks, but Gconf is besides my point, which is to make this setting settable and comprehendable for an average user.

Comment 7

[Wolfgang Rosenauer [:wolfiR]]

The above prefs were dropped completely. AFAIK for various reasons including missing UI (don't know all the reasons).
Protocol handlers are currently read from GConf (and partly gnome-vfs) only.
There is also the applications UI but this is not suitable right now for protocol handlers AFAICS.
I agree that the current situation (not speaking about TB2 anymore but FF>3.0 and TB>3.0) is not really satifying on Linux.

Comment 8

[Ludovic Hirlimann [:Usul]]

Bryan anyhting we could do in the 3.1 timeframe ?

Comment 9

[Yuri]

> The above prefs were dropped completely. AFAIK for various reasons including
missing UI (don't know all the reasons).

This doesn't sound good since there are a lot of useful values there to configure in the way known to many people (also common with FF). TB is often used in non-Gnome environments. This will force people to run gconf for TB settings even while in kde, which isn't nice.