Bug 120602 - New tabs should be shown instantly
Summary: New tabs should be shown instantly
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: internal browser (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 126413 130120 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-01-22 16:29 UTC by András Manţia
Modified: 2009-01-30 04:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description András Manţia 2006-01-22 16:29:33 UTC
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...
Comment 1 Frank Osterfeld 2006-01-25 22:34:51 UTC
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.
Comment 2 Frank Osterfeld 2006-07-03 19:47:59 UTC
*** Bug 126413 has been marked as a duplicate of this bug. ***
Comment 3 Frank Osterfeld 2006-07-03 19:48:33 UTC
*** Bug 130120 has been marked as a duplicate of this bug. ***
Comment 4 M G Berberich 2006-10-22 12:09:14 UTC
Now I have akregator 1.2.3 and KDE 3.5.3 and this annoying behavior still is there. 
Comment 5 monstermunch 2008-06-06 01:31:06 UTC
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.
Comment 6 Dotan Cohen 2008-12-29 15:01:00 UTC
> 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.
Comment 7 Dotan Cohen 2009-01-30 04:26:51 UTC
Fixed in KDE 4.2!