New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 5 users
Status: Fixed
Owner:
Closed: Nov 2010
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
Add x-scheme-handler/* MIME types to make Preferred Apps work in GNOME 3
Reported by zeut...@gmail.com, Nov 18 2010 Back to list
Chrome Version (from the about:version page): 9.0.576.0 (Official Build 65344) dev
Is this the most recent version: yes
OS + version: Fedora Rawhide
CPU architecture (32-bit / 64-bit): 64-bit
Window manager: GNOME 3

In the upcoming GNOME 3 desktop environment (and likely any other modern Linux system), the "Preferred Application" machinery relies on x-scheme-handler/* MIME types for generating a list of possible applications for "Web Browsing".

Therefore, Chrome should add x-scheme-handler/http and x-scheme-handler/https to the MimeType key in its .desktop file.

This GNOME bug is related: https://bugzilla.gnome.org/show_bug.cgi?id=635165

The thread discussing this new fd.o feature is: http://lists.freedesktop.org/archives/xdg/2010-October/011628.html

Thanks.
 
Comment 2 by hades...@gmail.com, Nov 18 2010
Note, you might also want to add "x-scheme-handler/ftp" as you handle FTP.
Labels: -Area-Undefined -Type-Bug Area-Compat-System Type-Feature
Status: Started
I already added the handlers for http(s) but it hasn't made it to release yet. I'll also add the ftp handler.
Comment 4 by f...@sofaraway.org, Nov 22 2010
fyi, i've already added (~a week ago) x-scheme-handler/http and x-scheme-handler/https to the MimeType entry of the desktop file i ship in my Ubuntu packages.
Comment 5 by f...@sofaraway.org, Nov 22 2010
see also https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/670128
Apparently, something else is needed to make chromium the default browser now.
According to https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/670128/comments/5, we need to run on Ubuntu 11.04:

xdg-mime default chromium-browser.desktop x-scheme-handler/http
xdg-mime default chromium-browser.desktop x-scheme-handler/https

Does this impact older/current distros that don't use x-scheme-handler?
Comment 7 by hades...@gmail.com, Nov 22 2010
> According to https://bugs.launchpad.net/ubuntu/+source/chromium-
> browser/+bug/670128/comments/5, we need to run on Ubuntu 11.04:
> 
> xdg-mime default chromium-browser.desktop x-scheme-handler/http
> xdg-mime default chromium-browser.desktop x-scheme-handler/https

You don't. You need a version of xdg-utils that supports x-scheme-handler/*. This is the work I did in the Red Hat bugzilla I mentioned above.

> Does this impact older/current distros that don't use x-scheme-handler?

It wouldn't, but I would strongly discourage you do this. There's a specific command to set the default handler.

FWIW, the errors running update-mime-database are just harmless warnings, which will be fixed in the next upstream shared-mime-info release, and the fact that it "doesn't work" when set in the GNOME default applications is completely unrelated. Maverick and Natty use GNOME 2.32, not GNOME 3.x, so the changes mentioned above have no bearing.

The problem is that Ubuntu ships a version of glib2 which has those changes, but none of the UI bits have followed.


So once you've added the x-scheme-handler/ mime-types, you can close this bug, the others are integration bugs in distros with mismatching versions of libraries and UI.
Status: Fixed
I've added the x-scheme-handlers. They'll show up in official dev channel builds with the 593 branch onwards. I'll worry about the other integration problems when F15 and Ubuntu Natty are closer to release.
Labels: -Area-Compat-System bulkmove Stability-Conflict
Project Member Comment 10 by bugdroid1@chromium.org, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Sign in to add a comment