What steps will reproduce the problem?
1. Goto Chrome's settings -> extended settings -> content settings
2. Disable JavaScript for all sites
3. Browse a site with JavaScript (both Chrome's and NotScript's icon will
appear in the address bar
4. Click NotScript's icon and choose "Allow" (the icon turns into a pyramid
with green box)
5. Refresh the page if NotScript does not automatically does
What is the expected output? What do you see instead?
NotScript's "Limitation" tab contains the following:
"All scripts loaded from a source location (the vast majority) can be blocked.
However, inline scripts that are directly written into the HTML code of a web
page cannot be blocked by NotScripts because Google Chrome does not fire load
events for them.
For example: <script src="http://example.com/aScriptFile.js"></script> can be
blocked without any issues. However, <script>alert("Hello, World!");</script>
written directly into the HTML code by the site you are visiting cannot be
blocked by NotScripts because it is not loaded from anywhere, it is a direct
part of the web page you view. However, these inline scripts are usually useful
and are often required for a site to function properly. If you want to, you can
set Google Chrome to deny javascript for all sites and use NotScripts to
selectively pick the scripts to run on sites you enable javascript on.
UPDATE: As of NotScripts V0.9.2 there is some inline script mitigation as a
stop gap measure to help a little until the extensions API is more robust."
So I did the steps above to test. But after allowing JavaScript for a site
(with NotScript, not Chrome), JavaScript is still blocked (no matter if inline
or not). I'd expect JavaScript is working afterwards, since the site is then in
the NotScript's Whitelist. Maybe you mean that you need to allow it with Chrome
(not NotScript), but then NotScript does not make any sense to me in this case?
What version of the product are you using? On what operating system?
NotScript: 0.9.6
Chrome: 20.0.1132.57
Please provide any additional information below.
Original issue reported on code.google.com by philip.ehret on 27 Jul 2012 at 11:08
Original issue reported on code.google.com by
philip.ehreton 27 Jul 2012 at 11:08