I threw my patch over the wall to xdg-utils upstream (which accepted the xdg-settings script from chromium). We'll see what they say about it, and if they like it, we can have chromium include an updated version.
Mario, the upstream version [1] does support looking at x-www-browser if not in GNOME, KDE, or XFCE4. Not quite what you were looking for, but it's a step. I'm not sure what you mean in comment 10. That we could rig GNOME to ignore its gconf keys in favor of x-www-browser? My understanding is that x-www-browser is a deprecated form of looking up the default browser (since each DE has its own way of setting it and exposing it to the user and none of them interact with x-www-browser). I guess that's what you want to fix, eh? :) Probably a different/bigger bug than this though.
I threw my patch over the wall to xdg-utils upstream (which accepted the xdg-settings script from chromium). We'll see what they say about it, and if they like it, we can have chromium include an updated version.
Mario, the upstream version [1] does support looking at x-www-browser if not in GNOME, KDE, or XFCE4. Not quite what you were looking for, but it's a step. I'm not sure what you mean in comment 10. That we could rig GNOME to ignore its gconf keys in favor of x-www-browser? My understanding is that x-www-browser is a deprecated form of looking up the default browser (since each DE has its own way of setting it and exposing it to the user and none of them interact with x-www-browser). I guess that's what you want to fix, eh? :) Probably a different/bigger bug than this though.
[1] http:// webcvs. freedesktop. org/portland/ portland/ xdg-utils/ scripts/ xdg-settings. in?view= markup