Bug 163867 - after opening image navigation buttons work incorrectly
Summary: after opening image navigation buttons work incorrectly
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-12 08:34 UTC by Andrew Belitsky
Modified: 2017-01-07 22:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Belitsky 2008-06-12 08:34:59 UTC
Version:           1.2.50 (using 4.00.82 (KDE 4.0.82 >= 20080610), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25-ARCH

1. open in tabs some page from feed;
2. on page click some link wich point to image.

Akregator will show image but when i click on navigation buttons it cause change of tab title but not page content.
Comment 1 Igor Știrbu 2008-07-03 11:29:07 UTC
Hello,

I have the same problem. I usually open links in
akregator tabs. Some pages may link directly to
images or pdf files. When an image or pdf file are
loaded by clicking on those links, the back button
will not load the page. The following popup appears:
"Could not open http://www.eliza.ch/documents.shtml"
and in the plugin where the pdf was opened the following
message is displayed for a few seconds:

Can not find a plugin which is able to handle the document being passed.

Thanks,
Igor Stirbu
Comment 2 Denis Kurz 2016-09-24 19:44:52 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 3 Denis Kurz 2017-01-07 22:16:51 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.