“Remove: Ad Scripts - Noscript” behaving

[whenever]

(Oct. 28, 2010 01:32 AM)JJoe Wrote:  The noscript block shouldn't be a problem when the browser has javascript enabled. The code preceding the noscript is javascript. The noscript should not execute.

People with javascript disabled in the browser would not need the exception.

The problem is Proxomitron doesn't know if the javascript is disabled or enabled in the browser.

(Oct. 27, 2010 06:21 PM)JJoe Wrote:  The filter uses a match in the noscript block to remove the noscript block and the chain of script blocks that precede it.

Why not just remove the noscript block?

I saw the quant script block preceding the noscript block was caught by "Block: Scripts by URL" filter when I added the noscript exception.

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.

Maybe sidki has some other considerations but .... Is he really leaving?