Bug in KURL handling(?)
faure at kde.org
Fri Jan 21 17:14:01 GMT 2005
On Wednesday 15 December 2004 21:58, Ingo Klöcker wrote:
> On Wednesday 15 December 2004 10:06, David Faure wrote:
> > On Tuesday 14 December 2004 13:31, Thiago Macieira wrote:
> > > The current behaviour is not acceptable, in which it displays # in
> > > the Location bar both for anchors and for %23.
> > This is not true - the location bar shows %23 for %23 (e.g. for a '#'
> > in a path).
> > The confusion in this thread seems to come from the assumption that,
> > in konq's locationbar, "when it starts with a slash it is a path" -
> > it is not so, it is still a URL, just without file:// in front.
> And that's probably the real problem. I'm 100% sure that my parents
> wouldn't identify a%23b (shown in the location bar) with the file
> called a#b. This is extremely confusing.
OK, I just fixed this. Now the location bar shows real paths when possible
(path, no ref, no query), and urls otherwise.
> FWIW, I just tried to following (Reminder: I'm using KDE_3_3_BRANCH): I
> created a file called 'a#b' in $HOME. Then I opened Konqueror and
> started to type "~/a" into the location bar. The auto-completion offers
> ~/a#b. I select it and press Enter. "The file or folder ~/a#b does not
> Huh? WTF? First Konqueror offers me the file via auto-completion and
> then it tells me the file doesn't exist? (Deja-vu? I have the uncertain
> feeling that I already brought exactly this example before.)
Well nobody cared about KURLCompletion for long, it seems.
> The only sensible solution for this whole usability mess is that
> anything without protocol is interpreted as path. And, of course, file
> URLs which are not just simple path must not be crippled because
> otherwise Konqueror won't understand them anymore correctly.
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel