Bug 179726

Summary:	next message keyboard shortcut incorrectly centers article title view
Product:	[Applications] akregator	Reporter:	Derek Harter <Derek_Harter>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	de.meyer.maarten
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Derek Harter 2009-01-05 16:50:26 UTC

Version:           1.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Debian stable Packages

When using left and right arrow keys to move to next/previous message, the message title preview pane is incorrectly centered.  Behavior seems to happen only when I am running a dual-monitor setup (laptop screen 1, monitor screen 2, fglrx video driver for an ATI video card).  In this case, it appears (to me at least) that a calculation is being made based on the size of the dual screen (2560x1024).  The size of the message title pane is very large, so a horizontal scroll bar appears in the pane.  And then, when moving to next/previous message using keyboard shortcuts, the pane view is centered, making it impossible to read the article title.

This behavior seems to have appeared after installing a fresh Ubuntu 8.10 distribution on my laptop.  Did not see it previously in Fedora 9 or Ubuntu 7/8.05

Comment 1 Derek Harter 2009-01-05 17:54:57 UTC

Realized that there were more columns than simply the title and by resizing the columns it reduces the width of the pane (and removes the horizontal scroll bar).

So the idea that it is related to the screen width may not be valid.  But I do still see the centering behavior on next/previous keyboard shortcut when the width of the columns is larger than the visible pane and thus a horizontal scrollbar is present in the pane.

Comment 2 Maarten De Meyer 2012-11-25 12:03:03 UTC

I can not reproduce this bug. What version are you using?
Could you post a screenshot of the problem.

Comment 3 Denis Kurz 2016-09-24 19:38:41 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:24:42 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.