Default browser setting

Rodney Dawes dobey at free.fr
Thu Jul 24 14:46:56 EEST 2003


On Thu, 2003-07-24 at 06:05, Waldo Bastian wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday 23 July 2003 23:17, Shaun McCance wrote:
> > > See the "mimetype standard" spec, and the proposed "mime-type/application
> > > mapping spec, being discussed roughly 2 weeks ago". Once those two specs
> > > are implemented in most desktops, finding what's the "preferred browser"
> > > is only a matter of looking up the preferred application for text/html.
> >
> > That doesn't seem right.  The "preferred browser" shouldn't be bound to
> > the mime type.  It should be bound to the scheme of the URL.  You don't
> > know that I'm going to get text/html from the server.  All you know is
> > that I've clicked an http link.  What mime type am I supposed to query
> > to find out what to use for mailto?
> 
> Not sure if it is an existing type already but the url/x-mailto idea that was 
> mentioned sounds interesting. Preferred browser could then be looked up by 
> checking for url/x-http.
> 
> The drawback would be that it does stretch the idea of mimetypes a little. 
> Does it make the mimetype of a URL such as "http://www.kde.org" url/x-http or 
> /text/html? That's rather context dependent I would imagine.

The url would fall under both mime types actually, depending on what the
default item sent from the server was. Typically it is text/html, but in
reality could be anything. The url mime type should be used only as a
fallback method to open a "web browser" for all http urls.

-- dobey




More information about the xdg mailing list