Version: 1.2.1 (using KDE 3.5.1, compiled sources) Compiler: Target: x86_64-suse-linux OS: Linux (x86_64) release 2.6.13-15.7-default Previously, when you clicked on a link/news item, akregator opened the new tab instantly and contacted the server/loaded the data afterwards. In the current 3.5 branch, there is a several seconds delay (maybe until there is an answer from the server?) between clicking and the tab appearing. This is bad, because on click nothing happens and I tend to click many times, resulting in several tabs with the same content...
This was changed to prevent the creation of unnecessary tabs - if you clicked e.g. on a PDF link, a tab was opened instantly and then the "open|save|cancel" dialog was shown after detecting the file is PDF. Now the tab is only opened if the type is HTML. On the other hand, it's annoying to wait for the server to respond. Another possible solution for 3.5.x would be to rely on the file extension.
*** Bug 126413 has been marked as a duplicate of this bug. ***
*** Bug 130120 has been marked as a duplicate of this bug. ***
Now I have akregator 1.2.3 and KDE 3.5.3 and this annoying behavior still is there.
Is anything going to happen about this? I agree the PDF related bug is a problem, but the most common use-case is opening regular html pages so the better trade-off is to have instant showing tabs. You could just make the PDF tabs close after the external viewer is launched. Either way, you want to give the user some feedback that a link has been clicked and is actually loading. Everyday, I'll click a slow site a couple of times when the link doesn't load because I'm not sure if it's being slow or I failed to click the link.
> You could just make the PDF tabs close after the > external viewer is launched. This is how the Mozilla extension handles the situation, and it works well. Both goals are obtained: the user gets feedback, and there are no redundant tabs left open.
Fixed in KDE 4.2!