Version: unknown (using KDE 3.1.93 (CVS >= 20031111), yes) Compiler: gcc version 3.2 OS: Linux (i686) release 2.4.21-1up.1 Currently, a freshly started Konqueror cannot open a second tab (Location -> New Tab is disabled) before some viewer part loads something in the current window. If you disable the Konqueror introduction in the web browsing view profile using config:/disable_overview, then Konqueror starts up with no part loaded (not even about:blank). The combination of these two features means that you cannot open multiple tabs in a freshly started Konqueror window. This might almost be OK, except that some actions (e.g., fetching a web page) do not display anything until some of the content arrives. So, if you open a slow-loading web page first, then you cannot open a second tab and do something else while you're waiting for the first tab to load. This limitation is also inconsistent with two other Konqueror behaviors: + You can always open a new window. "Open new tab" should be enabled whenever "open new window" is enabled. + If you already have multiple tabs, and the current tab is empty, then you can open a new window. (This may be because empty tabs are created with about:blank instead of nothing.)
*** This bug has been marked as a duplicate of 63873 ***
OK, Bug# 63873 is closed: as of KDE 3.2.1, "new tab" and "duplicate current tab" menu options are disabed when no part is loaded. This is a fine resolution for that bug, since that bug was reported as "normal", and is now fixed. However, I am reopening this bug, which is a "wishlist" request that these menu options *should* be enabled, and *should* do the expected thing. I wish that "open new tab" could be enabled whenever "open new window" is enabled, for the reasons I describe above. I suggest you try using browsing on dialup for a while --- you will find plenty of use for the "open new tab" action when no part is loaded in the Konqueror window.
I don't think this bug is fixed. When I write an url and press enter, I cannot do Ctrl+T to open a new tab until the first page has started drawing, so whit my slow connection this sucks.
well, perhaps it's fixed.
Yes, it's definitely fixed. Works here using KDE 3.3.