Yes, I have that filterset here in my default.cfg, but it is turned off. I was sitting here trying to remember why I turned it off in the first place, but could not really remember. When you mention it, I seem to remember that this was the exact reason. It killed a few things I wanted to preserve. But there is much to be learned in Paul's filterset which in fact is really good. So people should download it, try it out and have a look at the good coding in it.

this to let you know that in my filter set i have a different approach to tame javascript: i've simply realized 2 tame javascript [vm version] and 2 file, vmstart.js and vmend.js INCLUDING FILTERS in them, not simply js code.this way you can easily recognize what you need and what you can delete. this also allows user to add new code from his own filters. these files also are really simply to maintain.

edit:That doesn't mean Tame JS is the all in one solution for everyone.It can be too restrictive at times, and modifying the scripts is more difficult then switching of a filter

Paul Rupe is very helpful with these filters tho

I have emailed him several times, and have modified my version of start.js a bit, to allow certain functions (and disable others he does not include). I prefer using as little files as possible -- hence I put all the JS which is to be used always in start.js (or end.js), and all my user CSS which should always be used in prox.css.

but i suggest to not use bounds with this kind of filters because if you use bounds you need also to enable multi filtering, and this increase the time needed to filter the script. if you try to use bounds and not to enable the multi filtering you risk to not filter malicious code contained in the same script, so the filter is well written as it is now.