[Portland-bugs] [Bug 33055] Add xdg-browser or xdg-www

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=33055

--- Comment #7 from Binki <ohnobinki at ohnopublishing.net> 2011-06-20 06:54:30 PDT ---
(In reply to comment #5)
> OTOH, the command "xdg-open
> google.com" fails as it searches for a file named "google.com". These
> behavioural changes are important for some applications.

I agree with rdieter that this is intended/correct behavior. However, there's
also the case of a file in the current working directory called
http://google.com/ which would properly be accessed with something like
file://${PWD}/http://google.com/.

What we need to know is a proper way to get a browser launched without having
to specify some dummy URL. Or to be given a dummy URL which is guaranteed to at
least open a web-browser. Would something like

$ xdg-open about:blank

be suitable? I.e., is about: a protocol that is recognized by xdg-open as
something which a browser should deal with regardless of an about:blank file
existing in the current directory or could that be added?

With xdg-utils-1.1.0_rc1_p20110519, I found the following behavior:

The following works if there is no file called `about:blank':
$ xdg-open about:blank

The following opens in my browser, but my browser's launcher script realizes
that a file is being referred to and opens it as a file instead of using its
internal about:blank URL handler:
$ echo test > about:blank
$ xdg-open about:blank

The following opens the about:blank file with my ${EDITOR}:
$ echo test > about:blank
$ xdg-open file://${PWD}/about:blank

Here it looks like xdg-open is somehow interpretting `about:blank' as a
fully-formed URI but isn't convincing my browser to do so since my browser sees
the file...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.