Bug 118908 - using Konqueror/khtml configurations options
Summary: using Konqueror/khtml configurations options
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: internal browser (show other bugs)
Version: 1.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
: 111035 112382 156449 188455 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-23 14:40 UTC by Carsten Pfeiffer
Modified: 2017-01-07 22:23 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Pfeiffer 2005-12-23 14:40:06 UTC 
Version:           1.2 (using KDE 3.5.0, Debian Package 4:3.5.0-1 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.14.3

Hi,

it would be nice if akregator would reuse the Konqueror/khtml configuration by default or provide an own configuration (like it's already possible to change the font settings).

I.e. I would like disable plugins either entirely or for specific domains to avoid all those flash-ads.

Thanks,
Carsten
Comment 1 Frank Osterfeld 2006-01-28 15:32:42 UTC 
*** Bug 111035 has been marked as a duplicate of this bug. ***
Comment 2 missive 2006-09-13 23:44:15 UTC 
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.
Comment 3 David Bremner 2007-01-29 16:37:51 UTC 
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.
Comment 4 Marcin Trybus 2008-01-23 21:25:27 UTC 
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.
Comment 5 Eckhart Wörner 2008-01-24 19:28:05 UTC 
*** Bug 156449 has been marked as a duplicate of this bug. ***
Comment 6 Dominik Tritscher 2008-11-09 15:33:41 UTC 
Sounds more like a wishlist item then a bug report to me.
Comment 7 Dotan Cohen 2008-12-29 14:59:23 UTC 
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?
Comment 8 Maarten De Meyer 2012-11-14 13:32:29 UTC 
*** Bug 112382 has been marked as a duplicate of this bug. ***
Comment 9 Maarten De Meyer 2012-11-14 14:03:02 UTC 
*** Bug 188455 has been marked as a duplicate of this bug. ***
Comment 10 Denis Kurz 2016-09-24 19:40:03 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 11 Denis Kurz 2017-01-07 22:23:38 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.