Version: 1.1.1 (using KDE 3.4.1 Level "a" , SUSE 9.3 UNSUPPORTED) Compiler: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) OS: Linux (i686) release 2.6.11.4-21.7-default Keep the behaviour consistent with KMail/KNode so that when "Mark feed as read" action is initiated, then the next feed is opened. For 3.4.x if this could be the default it would be great, and maybe in 3.5 give a UI option to disable this.
As I see it, this option has a pro and con: pro: you are in the next feed after marking as read, which probably means you are "done" with that feed for now. So you can iterate over feeds with ctrl+r. con: the selection "jumps" without reason, which is confusing and maybe not wanted. I'd find it rather annoying and I don't see much use for iterating over feeds with ctrl+r (as there are other shortcuts for that). It is not default in KMail/Knode, maybe for a reason. If they make it default and someone persuades us why this is a great idea, we can adopt it. But I'll certainly never ever add config options for things like that.
*** Bug 315193 has been marked as a duplicate of this bug. ***
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
(In reply to Justin Zobel from comment #3) > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. The issue still exists on Akregator 5.15.3 (20.08.3)