Version: 3.5.3 (using KDE 3.5.3 Level "a" , unofficial build of SUSE ) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.16.13-4-default There is a difference in Javascript working depending on the fact whether I enable Javascript globaly for all sites or only for singular sites. At the page http://www.euronik.eu/en/map.html you find a JavaScript displaying a Google map. It works fine, when I enable JavaScript globaly (Only GUnload is missing, but that is not essential). When I disable JavaScript globaly and enable it only for www.euronik.eu, then it complains, that the variable GBrowserIsCompatible does not exist (which should be a function, no variable). I thus assume, the first JavaScript block is not loaded correctly. I enabled all the JavaScript sub settings (like open windows, ...) and the settings for the special site are set to using the global settings. This error makes the site-specific JavaScript settings pretty useless. There should be no difference in handling depending on the fact where I enable JavaScript. I assume this also explains the fact, that the problems I sometimes have with temporary enabling JavaScript throught the Extras menu HTML settings has the same reason.
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. ***
*** This bug has been marked as a duplicate of 102100 ***