“Remove: Ad Scripts - Noscript” behaving

[JJoe]

Is it fair to consider this problem to be user error? Many features of this set require javascript.

(Oct. 28, 2010 10:04 AM)whenever Wrote:  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.

I think unwanted noscript blocks are easier to detect than unwanted script blocks and usually preceded by at least one unwanted script. I have had something like this in my sets for a long time.

In no particular order or exhaustive:
A filter to remove unwanted noscript blocks could be added.
A change in the web bug filter could 'fix' some of these noscript blocks.
A filter to remove one script and noscript pair could be added. This filter must be activated by an exception that also deactivates "Remove: Ad Scripts - Noscript".

However, the web bug and script-noscript filters are less aggressive than they could be. I'm assuming that there are problems otherwise. I'm still examining the set and files.

(Oct. 28, 2010 10:04 AM)whenever Wrote:  Maybe sidki has some other considerations but .... Is he really leaving?

Sidki has posted about this more than once. I don't know much more.