Bug 127111

Summary:	Back button does not work correctly with frames
Product:	[Applications] akregator	Reporter:	Eckhart Wörner <ewoerner>
Component:	internal browser	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	geneseto, lemma
Priority:	NOR	Keywords:	triaged
Version:	1.2.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Eckhart Wörner 2006-05-11 00:09:57 UTC

Version:           1.2.2 (using KDE 3.5.2, Debian Package 4:3.5.2-2+b1 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-1-686

If one navigates inside a frameset in the embedded browser, the history of the back button does not reflect moves inside this frameset, it takes the user back to the last page before the frameset (or is disabled if no such page has been visited).

Comment 1 Ingo Malchow 2006-10-03 22:56:00 UTC

that is the exact behaviour like in konqueror AFAIK. Then it's maybe more a khtml issue?

Comment 2 Gene Seto 2008-11-24 00:03:13 UTC

Tested using r887704 compiled with gcc version 4.3.2 (Gentoo 4.3.2 p1.1). This bug still exists and is also in konqueror.  

Hum

Comment 3 Gene Seto 2008-11-24 00:07:20 UTC

watch carefully when you use the back buttons on this page. http://www.elated.com/res/File/articles/authoring/html/how-to-do-framesets/frame_examples/menuleft/index.html

Comment 4 Michael Leupold 2009-04-04 18:50:26 UTC

I can still reproduce this on KDE 4.2.0. Konqueror behaves right now, Akregator doesn't.

Comment 5 Denis Kurz 2016-09-24 19:39:00 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:40:39 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.