[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#308110: Launching on 'about:blank' loads no page; denies functionality.



On Mon, Jun 11, 2007 at 11:35:33AM +0200, David Martínez Moreno wrote:

> Hello, Adrian.  I do not understand completely your comment.
>
> If I run "konqueror about:blank" from konsole, I get a blank
> konqueror with the cursor ready in the location bar.  Isn't it what
> you want?

This behaviour is fine -- indeed, perfect -- and is precisely the
reason I still use "konqueror about:blank" as my launch shortcut.

The bug in this case is that a large portion of Konqueror functionality
is disabled in this initial state.  It is as if Konqueror is only half
leaded.

Examples:

* I cannot open new tabs.  Since this condition is not remedied until
  after I successfully access a webpage, if the website I try to
  access is slow or down, I cannot open a new tab to initiate a second
  request while waiting for the first.

* I cannot stop a request from loading.  In this case, the menu actually
  shows the 'stop' option, but neither the menu option nor the keyboard
  command (escape) has any effect.

  This is particularly annoying when combined with the 'cannot open
  new tabs' issue.  A common scenario:  I enter a URL, but it is
  taking a long time to load.  Since I cannot open a second tab, I
  instead hit escape and type in a different URL.  However, in the
  middle of entering the second URL, the first URL loads, erasing the
  second URL I was typing.

* The entire 'Tools' menu is nonfunctional.  Most options are missing;
  the only two available options are disabled.  I cannot, for example,
  disable or enable the use of the HTTP proxy/cache, nor access the list
  of crashes in case my last session crashed.

* I cannot show or hide the menubar.  If I am unfortunate enough to
  have exited a prior session with both the location bar and menu bar
  disabled (which I occasionally do for demonstrations), I am not
  aware of any way to proceed; I have to exit and launch on a
  different URL.

There are likely other issues, but these are the ones that come up the
most often.

I still use Konqueror in this state simply because the majority of
launches don't invoke any of the above issues.  However, I reported this
bug because they do occur (under my own personal usage pattern), and I
was hoping the underlying issue could be dealt with.

Regardless of the cause, it still seems odd to me that I can launch
"konqueror about:blank" and end up in state A, then type "about:blank"
into the location bar and end up in (drastically different) state B.

Attachment: signature.asc
Description: Digital signature


Reply to: