Bug 227005

Summary:	inaccurate internal links in internal browser when font size is increased
Product:	[Applications] akregator	Reporter:	Bourdieu <mathieu.bouillaguet>
Component:	internal browser	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	moltonel
Priority:	NOR
Version:	1.5.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bourdieu 2010-02-15 14:57:07 UTC

Version:           1.5.3 (using 4.3.4 (KDE 4.3.4), volkerdi@slackware.com)
Compiler:          gcc
OS:                Linux (i686) release 2.6.32.7-smp

When viewing an article in the internal browser of akregator, if you increase the size of the font when you click on an internal link in the article, the frame does not scroll to the precise location of the corresponding <a> tag.

The frame does not scroll enough when the font is bigger than the default size. The more you increase the font size the farther the frame end up from the right location.

The frame should scroll to the exact same place no matter what font size you choose.

The same behavior is present in konqueror 4.3.4. This bug looks like a bug related to khtml but it impacts directly akregator

Comment 1 Vincent de Phily 2010-02-17 00:47:58 UTC

I can confirm this in akregator and konqueror when zooming everything (text+images+style) but not when zooming the text only. KDE SC 4.4.0.

Comment 2 Bourdieu 2010-02-17 01:00:48 UTC

I don't know what you mean by "zooming everything (text+images+style)". To increase the size of the font I use the keyboard shortcut Ctrl++ or Ctrl + Mouse scroll wheel up.

This increases only the size of the font of the text, the images are unchanged.

Comment 3 Vincent de Phily 2010-02-17 14:52:53 UTC

Khtml can either zoom just the text (ctrl++) or zoom everything (ctrl+mousewheel). I can only reproduce the bug you describe when zooming everything. kde 4.4.0, gentoo & arch packages.

Comment 4 Bourdieu 2010-02-17 15:25:04 UTC

You're right. It only happens when zooming everything.

Comment 5 Denis Kurz 2016-09-24 19:45:30 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 6 Denis Kurz 2017-01-07 22:50:16 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.