1005626 - x-scheme-handlers in .desktop files mostly ignored by Firefox

Status: RESOLVED WORKSFORME

(Firefox :: Shell Integration, defect)

Description

[Toni Spets]

Attachment: foo.desktop

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140428120048

Steps to reproduce:

1. Create a valid .desktop file with x-scheme-handler
2. Place it in either /usr/share/applications or ~/.local/share/applications
3. Do whatever steps are required to refresh the desktop file into your system (update-desktop-database or kbuildsyscoca4 on KDE)
4a. Verify that the desktop file URI association works with "xdg-open foo://" in a terminal
4b. Verify that the desktop file also associates with your applications menu and it works
5. Go to "foo://" in Firefox


Actual results:

Firefox does *not* list your application in the "Launch Application" dialog and you need to manually select the binary making .desktop files completely useless for protocol association.


Expected results:

Have an option in the dialog to use the installed .desktop file association.

Comment 1

[Toni Spets]

As used in Bug 727422, this python snippet does show the proper handler on my system:

    $ python -c 'import gio; print gio.app_info_get_all_for_type("x-scheme-handler/foo")'
    [<gio.unix.DesktopAppInfo at 0x12dfe10: Foo XTerm>]

Still, for whatever reason, Firefox does not offer "Foo XTerm" as an option to handle the foo:// protocol.

Comment 4

[Jan Horak [:jhorak]]

This works for me on Fedora 20 with Firefox 31.

Comment 5

[Elad Alfassa]

Works for me too on Fedora 21 with Firefox 32.

Comment 6

[Toni Spets]

I can also confirm it now works on Firefox 31 on Fedora 20. The foo:// protocol is properly in the list and I haven't touched the .desktop file after reporting.

However, the actual commit that fixed it would be nice to point out and possibly backport to ESR as it makes programs like Steam work unreliably with steam:// links on systems that do not follow the stable channel.

Thank you for fixing it, whoever it was.

Comment 7

[Toni Spets]

Scratch that, read the ESR policy again (only security fixes) and 31 was also recently released as ESR so the fix should already be in.