Hi Dch48,
But all these scanning formula's are scanning after the fact. It is not for nothing that avast brought shield scanning to the browser. But also this detection in real time and blocking depends on what is implemented and not. Good example is a lot what avast! detects is not detected by DrWeb's and v.v. Sometimes a scan is flagged but the malware is already taken down or not responding, but also the opposite will produce missed detections. In some browsers (not IE) we have the google safebrowsing alerting not to visit certain pages. In IE a lot is scanned by Windows Defender in the background (see your event viewer for details like %%807 alerts). Blocklists are as good as those that produce them. So scanning is running behind the actual facts.
NoScript and ScriptSafe is not because it always protects under all circumstances and for all script malware. Normally a lot of bad iframe malcode and malicious obfuscated code is being missed, NoScript cannot miss as it blocks this. But there are users that cannot make themselves use this extension, so be it.
Let them do a full scan of the browser file location after aa browser session has ended, avast! finds a lot that way, and regularly empty the browser cache.
The only alternative that I can see that equals remotely browser script blocking of suspicious and remote scripts is working the browser in a sandbox and or VM (certainly for risky browsing) to be able empty the sandbox as if the browser session never existed...
polonus