| Summary: | rekonq tries to open iFrames instead of displaying them | ||
|---|---|---|---|
| Product: | [Unmaintained] rekonq | Reporter: | Elias Probst <mail> |
| Component: | general | Assignee: | Andrea Diamantini <adjam7> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | apaku, kamikazow, pano9000 |
| Priority: | NOR | ||
| Version First Reported In: | 0.4.90 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Elias Probst
2009-08-08 18:03:33 UTC
I can confirm this :-) Quite strange but.. it seems working now. At least in my box. But I don't know why.. (In reply to comment #2) > Quite strange but.. it seems working now. At least in my box. But I don't know > why.. Confirmed and closed On Monday 10 August 2009 18:15:15 Elias Probst wrote:
> https://bugs.kde.org/show_bug.cgi?id=203097
>
>
> Elias Probst <mail@eliasprobst.eu> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - Status|NEW |RESOLVED
> Resolution| |FIXED
>
>
>
>
> --- Comment #3 from Elias Probst <mail eliasprobst eu> 2009-08-10 18:15:14
> --- (In reply to comment #2)
>
> > Quite strange but.. it seems working now. At least in my box. But I don't
> > know why..
>
> Confirmed and closed
>
btw, it has to be a KIO::AccessManager gift :)
*** Bug 217521 has been marked as a duplicate of this bug. *** *** Bug 237617 has been marked as a duplicate of this bug. *** Why has this been closed? The suggested changes have been done sometime last year, I've reported my problems 2 weeks ago running rekonq on an up-to-date trunk of kdelibs. So its definetly still there. So was something done in rekonq's source to fix this? If so a link to the change would've been nice, or at least a note that its been fixed in rekonq Your report was closed, because it's a dupe. And accidentally I closed you report as dupe of this bug and then you've got me confused, so I reopened this bug (which was wrong). You're looking for Bug 217521 |