Summary: | using Konqueror/khtml configurations options | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Carsten Pfeiffer <pfeiffer> |
Component: | internal browser | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | dietz, dominik.tritscher, kde-2011.08, kde, miro.doma, missive, monstermunch, mtrybus |
Priority: | NOR | Keywords: | triaged |
Version: | 1.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Carsten Pfeiffer
2005-12-23 14:40:06 UTC
*** Bug 111035 has been marked as a duplicate of this bug. *** I just realized that Akregator has javascript enabled, while I have javascript disabled in konqueror. I agree that the browser component of akregator should either re-use the global browser settings, or at least be configurable in the same way. I would like to be able to configure the konqueror plugin from within akregator. I often seem to be changing image viewers these days, and it takes me a second to realize I have to pull up konqueror to configure the file type associations. Bug 156449 (titled "Web pages opened in akregator do not follow konqueror's accessability CSS setting") I submitted today seems to be yet another case of this bug. *** Bug 156449 has been marked as a duplicate of this bug. *** Sounds more like a wishlist item then a bug report to me. Actually, I agree that this is a bug and not a wish. KDE configuration of internet browser preferences is done in Konqueror, as that is the official KDE browser. All other KDE apps should respect that. Can someone think of a use case where one would need different configuration in Akregator than in Konqueror, as default? *** Bug 112382 has been marked as a duplicate of this bug. *** *** Bug 188455 has been marked as a duplicate of this bug. *** 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. |