Summary: | Javascript difference between global enabling and per site enabling | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Dirk Stoecker <kde> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Dirk Stoecker
2006-07-13 18:00:10 UTC
One additional note: After some investigation I found the source. As the javascript itself is loaded from the ggogle page, it gets blocked. There are 3 possible solutions to this: a) In case JavaScript is allowed on page foo and load from bar gets block, a warning request should be displayed to tell it to the user. The user may then add the blocked site as well. b) In the site specific JavaScript selection add an option, which allows to execute JavaScript from directly referenced sites as well. c) Add an option like b), which allows to execute every JavaScript which may also be referenced indirectly from the base site (multiple levels). *** Bug 127123 has been marked as a duplicate of this bug. *** |