Bug 197175 - When showing complete website for RSS feed items akregator doesn't start at the top
Summary: When showing complete website for RSS feed items akregator doesn't start at t...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 18:33 UTC by Gandalf Lechner
Modified: 2017-01-07 21:50 UTC (History)
1 user (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 Gandalf Lechner 2009-06-19 18:33:44 UTC
Version:           1.4.50 (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-13-generic

This bug occurs when you use the option "load complete website" for some RSS feed. When you read the website of some feed item, scroll down a bit to read more, and then use your shortcut key to jump to the next unread item, akregator doesn't show the top of the website related to this item, but rather scrolls automatically to the position where you left the previous site. 
Clearly, it should start at the top so that the user can read the new site from its beginning.
Comment 1 Frank Osterfeld 2009-06-27 22:39:51 UTC
Cannot reproduce. Here it always resets the position to the top - no matter if the item content or the linked website is loaded.
Comment 2 Gandalf Lechner 2009-06-29 09:53:11 UTC
I experience this behaviour with the feeds from http://www.spiegel.de/ - maybe its a problem of that site?
Comment 3 Denis Kurz 2016-09-24 19:39:25 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:50:18 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.