“Remove: Ad Scripts - Noscript” behaving

[whenever]

(Oct. 29, 2010 07:11 PM)JJoe Wrote:  Less aggressive brings ads and/or unwanted behaviour. More aggressive may break more pages. I'm sure it can never be perfect.

If 90% of the browser has javascript enabled, less aggressive means we might miss some ad noscript blocks, which in fact won't be executed by the browser, so it won't bring ads; more aggressive means we have more opportunity to kill good scripts and to break pages.

(Oct. 29, 2010 07:11 PM)JJoe Wrote:  Any ideas to make things better?

I don't know. My initial thought was:

(Oct. 28, 2010 10:04 AM)whenever Wrote:  It seems better for noscript filter to remove ad noscript blocks only and script filter to block ad script blocks only. Let them do their job separately.

but if 90% of the browser has javascript enabled, AND if web bug is the most common annoyance of noscript blocks, I prefer a less aggressive policy because it won't break page and won't bring ads. Maybe we don't need a dedicated filter for noscript block, and can just change the web bug filter to handle the noscript block, as you had suggested.