Point of "Malformed URL" message boxes

Koos Vriezen koos.vriezen at xs4all.nl
Thu Sep 23 20:20:28 BST 2004


On Thu, Sep 23, 2004 at 12:45:18PM +0200, Koos Vriezen wrote:
> On Thu, Sep 23, 2004 at 10:35:23AM +0200, David Faure wrote:
[..]
> > Well usually an error happens after the user tried to open something, so it's very
> > useful to tell the user why the opening failed (try typing "gg:" in konq's location bar).
> > On that site though, from what you say, it's about some URL that is opened
> > as a side effect (redirection? frame? although frame error usually show up inside
> > the frame...)
[..]
> if javascript tries to open invalid URLs (not to mention the annoyance
> of having to click on 'Ok' buttons, a less intrusive sliding message,
> like konsole uses often when typing 'exit', would be better). A
> "Malformed URL" message is not user friendly (and for a lot not
> informative at all *) esp. when it comes from javascript.
> 
> *) Invalid location given (gg: has no hostname)

Thinking about this, common libraries shouldn't popup message boxes at
all. Indeed, like you said, how does it know if it's an user or machine
generated is calling. Me thinks it should return -EMALFORMEDURL or throw
a KIOMalformedUrlException object with some hints what was wrong, and
location bar can show a message to the user while kjs triggers a script
error, no?

Koos




More information about the kfm-devel mailing list