Bug 126413

Summary:	browser-tabs open too late on slow connections
Product:	[Applications] akregator	Reporter:	M G Berberich <kde>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:

Description M G Berberich 2006-04-28 12:51:19 UTC

Version:            (using KDE KDE 3.5.1)
Installed from:    Debian stable Packages

akregator in 3.5.1 does open it's integrated browser-tabs only when it has etablished a connection (or so), in 3.3.2 the tab was opend (empty) immediately. This is a problem because:

a) klicking on a entry does no longer provide _any_ feedback to the user. In 3.3.2 the window opened and the user knew the klick has been registrated, now nothing happens until tens of seconds later when using a slow dialup-connection.

b) The behavior is different than in konqueror where the tabs opens up immediately empty and then loads the contents. The user expects same behavior as konqueror because the applications do something similar (displaying webpages)

The current behavior is irritating at least.

Comment 1 Teemu Rytilahti 2006-04-28 20:59:55 UTC

Yes, this is the new behaviour which makes it possible not to have "empty" tabs. IMHO the old behaviour is better and we should use Konqi style "connection timeout" page when appropriate.

Comment 2 Frank Osterfeld 2006-07-03 19:47:57 UTC


*** This bug has been marked as a duplicate of 120602 ***