Bug 132384

Summary: Better wildcard support for Konqueror's ability to whitelist JS
Product: [Applications] konqueror Reporter: Stephan Sokolow <kde_bugzilla_2>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Stephan Sokolow 2006-08-14 12:55:32 UTC 
Version:           3.5.2 (using KDE 3.5.2, Gentoo)
Compiler:          gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.16-gentoo-r9-20060701

Konqueror's ability to enable JS on a per-site basis doesn't allow wildcards. This makes it useless for anyone who regularly uses sites like deviantart which use subdomains heavily.

I use deviantART as an example for two reasons. First, it's a very well-known and popular site. Second, every user's page is it's own subdomain.
Comment 1 Stephan Sokolow 2007-03-30 09:09:36 UTC 
C'mon guys. Let's get more votes on this.

The whitelisting feature is nearly useless to me until this problem is fixed and, now that Jikto has proven how dangerous untrusted JS could potentially be, I'd really like to start doing some whitelisting.

(I use a lot of sites which use subdomains the way deviantART does)
Comment 2 Stephan Sokolow 2007-04-02 09:02:33 UTC 
Well, looks like I was mistaken. It does support wildcards, but in a very un-intuitive (and apparently, undocumented and relatively little-known) fashion.

When I was typing "*.deviantart.com" and "rs*.rapidshare.com", I should have been typing ".deviantart.com" and filing a bug about the limitations and relative secrecy of existing wildcard support.

Can I get this changed to a feature request named "Better wildcard support for Konqueror's ability to whitelist JS" or should I close this and open a new one?
Comment 3 Tommi Tervo 2007-04-02 09:13:31 UTC 
#134169 has more details

*** This bug has been marked as a duplicate of 134169 ***