Version: 1.6.2 (using 4.4.2 (KDE 4.4.2), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.33.2 When I select WebKit (kwebkitpart) as embedded viewer for text/html then the Akregator's Back and Forward buttons are not click-able while I'm browsing the news sites after I clicked an RSS link. With KHTML as engine the buttons are working properly!
I can confirm this bug
*** Bug 243370 has been marked as a duplicate of this bug. ***
Well, I guess this bug report was waiting from my input. From what I have been able to tell by enabling debugging, this problem stems from the fact that akregator uses a "hack" it copied from kdevelop to make history navigation work. Unfortunately, the so called "hack" is exactly that, a hack. An unnecessary one at that if you ask me. The proper way to update your history list is to listen for the KParts::BrowserExtension::openUrlNotify singal. As the documentation explains, once you receive that signal, just query the KPart for the url. However, that is not what akregator does. It does not even connect to the aforementioned signal and as such whatever hack it is using is only applicable to khtml because KHTML uses the KPart's openUrlRequested signal to fulfill each and every request including the clicks on links.
*** This bug has been confirmed by popular vote. ***
*** Bug 311255 has been marked as a duplicate of this bug. ***
*** Bug 310132 has been marked as a duplicate of this bug. ***
*** Bug 342034 has been marked as a duplicate of this bug. ***
Am Freitag, 19. Dezember 2014, 17:50:24 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=233734 > > Jonathan Marten <jjm@keelhaul.me.uk> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |Martin@Lichtvoll.de > > --- Comment #7 from Jonathan Marten <jjm@keelhaul.me.uk> --- > *** Bug 342034 has been marked as a duplicate of this bug. *** Bummer, I didn´t see this one while entering searching "WebKit" as search term in the duplicate search field. Thank you,
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.