Version: 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1) (using 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1), Kubuntu packages) Compiler: gcc OS: Linux (x86_64) release 2.6.24-18-generic When middle-clicking links in konqueror to open new tabs, there is a significant delay between when the user middle clicks and when the new tab appears. It seems that the tab does not appear until some communication with the linked website is made. This is especially apparent for slow websites (try bugs.kde.org; page loading is usually fairly sluggish). The problem with this is that the delay in the tab appearing gives konqueror a sluggish feel and the impression that it is unresponsive. Also, you may think you haven't made the middle-click when you did and click again. I find konqueror is a fast browser with good performance, but it's small issues like these that can make the browser appear as if it slow when really it is just a design choice about when to display the new tab. I think a better solution would be to instantly display a tab with a small loading icon.
I've noticed the same problem. Tabs should be opened faster.
By the way, I didn't have firefox installed before to try this, but firefox shows tabs instantly with a "Loading..." message on them and a loading animation. I just noticed that KDE3's konqueror does display new tabs instantly with the website address dimmed out (which I think is better than firefox as this is more informative). If you try browsing on konqueror3, firefox and konqueror4, konqueror4 just feels painfully slow compared to the others even though the loading speed is exactly the same. I think this is a real shame as it's clearly an optimised browser and it's just a very small issue about when you display things that makes it feel slow. For instance, try opening a link from bugs.kde 5 times or so quickly by middle-clicking and you'll find konqueror4 just feels sluggish in comparison as it doesn't respond instantly.
This is true and it has bugged me too. I think this is a regression because it wasn't happening in konqueror from KDE 4.0, and not even in KDE 4.1 until recently.
I don't know how slow it is for you, but I am noticing a delay of as much as three seconds before there is any reaction from the browser at all. In that time, I am likely to click again at least once, resulting in multiple tabs opening. Even after it starts to react, all it does it open a tab as wide as the favicon. Then, another whole second later, it widens to normal width, and one can go to see whether the page has loaded yet or not. Subsequent clicks work faster. But they still take a good second to open the tab properly. I notice that people are comparing this to Firefox. That's actually setting the bar a bit too low. Firefox is sluggish compared to Opera, which opens tabs truly instantaneously no matter what.
*** Bug 164742 has been marked as a duplicate of this bug. ***
*** Bug 164820 has been marked as a duplicate of this bug. ***
Ah, I see. I made konqueror wait for the mimetype before opening the tab, to avoid a useless blank tab when opening the target (e.g. a PDF) into a separate application (r805892). But indeed this makes konq less responsive, I guess I should go back to the original behavior... I wonder what other browsers do when they launch a separate application instead of opening the URL in the tab?
OK, firefox does like kde3-konqueror: useless empty tab remains.
Maybe you could just close the tab again as soon as you know what to do with the data? Also not perferct because tabs jump around a bit but you're right, those empty blank tabs always annoyed me as well :)
Exactly, jumping tabs (when you might be clicking on one) are a bit too much magic behavior, so I wasn't decided on doing that. Even when double-checking that the tab is still empty (of course). But I'll at least fix the ugly 100x30 white rectangle and the spinning wheel... (and "Loading..." as label is a good idea - after the 4.1 message freeze)
SVN commit 824504 by dfaure: Restore the code that I removed in r805892 with the idea of fixing the empty useless tab after MMB opens a separate application. It was a good idea, but now when doing MMB the user has no visual feedback that a tab is going to be created, so not such a good idea after all. So better keep the empty tab, like firefox does. Fixed one bug with that situation: statusbar was still showing a progress message, now it's cleared. + a TODO for showing "Loading..." in the tab after the kde-4.1 message freeze. BUG: 163628 M +38 -14 konqmainwindow.cpp M +1 -1 konqopenurlrequest.h M +5 -1 konqrun.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=824504