Bug 192645 - unable to deactivate java script in akregator
Summary: unable to deactivate java script in akregator
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-14 11:54 UTC by Karsten König
Modified: 2017-01-07 21:58 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 Karsten König 2009-05-14 11:54:59 UTC
Version:           1.4.2 (using KDE 4.2.3)
OS:                Linux
Installed from:    SuSE RPMs

from novell bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=325627

Copy for convenience
"I disabled JavaScript in Konqueror completely for security. However Tabs that
are opened from Akregator still use JavaScript. After making the same page
independent it is displayed without JavaScript."

I can confirm this on 4.2.3, I haven't tested further how or if any settings made in konqueror are used in akregator
If the html settings are per application there should be a way to access them

Thanks! =)
Comment 1 Christian Jann 2011-09-05 13:57:42 UTC
Still valid in Akregator version 4.7.0 when using kwebkitpart, there should really be a way to set this individually
for Konquerror, Akregator and rekonq.
Comment 2 Christian Jann 2012-01-18 19:39:52 UTC
I've found a way:

open Konquerors configuration and copy some parts to akregator and kontact:

vim .kde/share/config/konquerorrc
vim .kde/share/config/akregatorrc
vim .kde/share/config/kontactrc

[Java/JavaScript Settings]
AppletServerTimeout=60
ECMADomains=
EnableJava=false
EnableJavaScript=false
EnableJavaScriptDebug=false
EnablePlugins=false
JavaArgs=
JavaDomains=
JavaPath[$e]=java
PluginDomains=
ReportJavaScriptErrors=false
ShutdownAppletServer=true
UseKio=false
UseSecurityManager=true
WindowFocusPolicy=0
Comment 3 Denis Kurz 2016-09-24 19:38:01 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 4 Denis Kurz 2017-01-07 21:58:28 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.