Bug 226814

Summary: Article view automatically proceeds to a popup-like page
Product: [Applications] akregator Reporter: Christoph Lange <langec>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christoph Lange 2010-02-14 14:53:52 UTC
Version:           1.6.0 (using 4.4.00 (KDE 4.4.0), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.31-thinkpad

When reading articles from this feed (http://arstechnica.com/features.rssx), the article view (i.e. the KHTML tab displaying the article) frequently jumps to a page that doesn't display anything, or maybe a whole page Flash applet, I have Flash disabled.  The page is titled “Dart Frame”.  When I navigate back to the article page, Akregator instantly jumps back to the “Dart Frame” in most cases.  That makes it impossible to read an article.  When I open the same article in a browser (e.g. the article http://arstechnica.com/apple/reviews/2010/01/mac-mini-with-snow-leopard-server-review.ars/), it usually works.

Note:
* I have not _really_ intensively tested this with Konqueror, as I mostly use Firefox for browsing.  But with Firefox I have never had trouble so far.
* Often the problem does not occur on the first page of an article, but on any subsequent one.
* In the source of the page there is some JavaScript containing the string “dart”, that looks like the culprit.
Comment 2 Christophe Marin 2010-02-22 00:23:28 UTC
Looks related to their ads banner. Did you turn the adblocker on ?
Comment 3 Christoph Lange 2010-02-22 00:26:12 UTC
(In reply to comment #2)
> Looks related to their ads banner. Did you turn the adblocker on ?
No, I didn't.  How would I have to configure it in order to avoid that problem?
Comment 4 Denis Kurz 2016-09-24 19:42:46 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 5 Denis Kurz 2017-01-07 22:01:47 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.