Version: (using KDE 4.2.96) Installed from: Ubuntu Packages When I click on a link which opens a file (PDF, PNG) embedded in a tab, there is no possibility to go back in browsing history as it is possible in other tabs. It does not work with assigned key for going back and also does not appear in the context menu.
Can't reproduce. Can you describe your steps in more detail? What I tried: Open "Complete Story" link for an article that contains a link to a PDF => Tab opened with article website in it click PDF link => Same tab opens PDF in okular KPart Going back to the previous HTML page and then forward again to the PDF work here, both using the toolbar actions and the shortcuts.
Here is an example with an PNG which I can reproduce: http://frinring.wordpress.com/2009/09/19/polishing-the-tools-for-okteta-0-4/ Click on the picture, you wont find a way to get back to the page that linked it. I noticed that the problem does not occur allways (when I was searching for an example, because this problem has bothered me quite often recently, it suddendly seem to work, but the above should show the problem)
Another example: http://kde-apps.org/content/show.php/Copy+file+or+directory+path?content=112873 If I choose to download this file, it is automatically opened in an editor (another bug from my point of view, reported here: http://bugs.kde.org/show_bug.cgi?id=209067 ) When the editor is opened I do not have the possibility to go back in the tab history.
Another example, now running with KDE 4.3.2 http://bangarangkde.wordpress.com/2009/10/07/intro/ click on the image, going back is not possible.
Actually, I never get a browsing history when opening stories in a tab. Back/forward buttons always stay greyed out - this happens with regular links on regular websites. KDE-4.9.1 here
Setting status to confirmed.
(In reply to comment #5) > Actually, I never get a browsing history when opening stories in a tab. > Back/forward buttons always stay greyed out - this happens with regular > links on regular websites. Same here: KDE SC / Akregator 4.10.2
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.
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.