Bug 232831

Summary:	Saving scroll position is broken
Product:	[Applications] kdepim	Reporter:	Thomas McGuire <mcguire>
Component:	messageviewer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	LO	Keywords:	akonadi-ports-regression
Version:	4.5
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description Thomas McGuire 2010-03-31 13:37:51 UTC

The scroll position is not restored after the viewer is updated, for example after collapsing some quotes or after the signature was verified.

See code in ViewerPrivate::updateReaderWin().

Comment 1 Laurent Montel 2011-09-01 17:58:39 UTC

How to collapse some quote ?

Comment 2 Thomas McGuire 2011-09-01 18:13:56 UTC

If you have qouted text, like
> bla bla bla
> bla bla bla

Then a collapse icon should appear.on the left of the text. It needs to be enabled at Settings->Appearance->Message Window->Show expand/collapse quote marks first.

Comment 3 Laurent Montel 2011-09-01 19:22:05 UTC

Ok I can confirm this bug
Will look at how to fix it.

Comment 4 Laurent Montel 2011-09-01 19:44:10 UTC

void MailWebView::scrollToRelativePosition( double pos )
{
  // FIXME: This doesn't work, Qt resets the scrollbar value somewhere in the event handler.
  //        Using a singleshot timer wouldn't work either, since that introduces visible scrolling.
  const int max = page()->mainFrame()->scrollBarMaximum( Qt::Vertical );
  page()->currentFrame()->setScrollBarValue( Qt::Vertical, max * pos );
}
ok it's a known bug

Comment 5 Denis Kurz 2016-09-24 21:00:04 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 kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 22:35:46 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.