Bug 134169 - JavaScript Domain-Specific settings are a bit confusing.
Summary: JavaScript Domain-Specific settings are a bit confusing.
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
: 132384 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-16 16:51 UTC by Matt Sicker
Modified: 2023-01-22 05:05 UTC (History)
2 users (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 Matt Sicker 2006-09-16 16:51:06 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
Compiler:          gcc 4.0.3 (ubuntu) I don't think this matters much
OS:                Linux

Let's say you wish to enable JavaScript for an entire domain (e.g. kde.org).  Enabling 'kde.org' will only enable 'http://kde.org/*'.  So we want to enable the whole domain, right?  We try '.kde.org' since that means "all of kde.org" in RFC 2109 (cookies).  However, this only enables all the subdomains of kde.org, thus excluding 'http://kde.org/*'.  Therefore, there are no [easily available] methods to enabling or disabling JavaScript per domains.

I would also suggest that the addition of wildcards for this would be helpful in order to specify more specific URLs (e.g. 'https://mail.google.com/mail/' or 'www.google.com/ig').  This would be useful for cookies and other filters as well.  Basically, what I'd want here is the ability to specify protocols, how much of the domain (root or subdomains), and specific directories.  It'd be useful to allow regexps for this now that I think about it.

Overall, fixing these two things should help clarify the configuration for domain-specific JavaScript, cookie, proxy, plug-in, et al., settings.
Comment 1 Tommi Tervo 2007-04-02 09:13:33 UTC
*** Bug 132384 has been marked as a duplicate of this bug. ***
Comment 2 FiNeX 2008-06-01 14:57:16 UTC
Still valid for 3.5.9 and KDE 4.
Comment 3 Janek Bevendorff 2012-06-18 19:39:52 UTC
There hasn't been any activity on this issue for some time. Please check if this issue is still valid for Konqueror 4.8.4 or later.
Comment 4 Andrew Crouthamel 2018-09-23 02:18:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Stephan Sokolow 2018-10-13 09:35:00 UTC
Sorry for the delay.

Problem is still present in Konqueror 4.13.3.

If you want a test under KDE 5, let me know and I'll see if I can borrow a machine running something newer than Kubuntu 14.04 LTS.
Comment 6 Stephan Sokolow 2018-10-13 09:51:39 UTC
Woops. Forgot to set the status.

(I'm too used to Mozilla's Bugzilla instance, where needinfo is a flag with the "clear needinfo" checkbox checked by default.)
Comment 7 Justin Zobel 2022-12-01 04:34:33 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-12-16 05:13:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Stephan Sokolow 2022-12-23 06:34:24 UTC
I don't currently have time to test a feature I no longer use... especially when prep for upcoming Christmas holidays is more important than some kind of automated "test this or let us close your bug" message and I don't even have Konqueror *installed* anymore.
Comment 10 Bug Janitor Service 2023-01-07 05:21:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Bug Janitor Service 2023-01-22 05:05:30 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!