“Remove: Ad Scripts - Noscript” behaving

[whenever]

Another idea is to limit the filter to match max. 2 script blocks that are preceding to noscript blocks, since tracking code usually has script and noscript blocks appear in pair and close to each other. This policy seems more reasonable and is not that aggressive like sidki's.

Changing below code:

Code:

([ \t\r]+(\n[ \t\r]+)+{0,2}$NEST(<script,>)( $NEST(<script,>))+$INEST(<script,</script)</script*>)+

to:

Code:

([ \t\r]+(\n[ \t\r]+)+{0,2}$NEST(<script,>)( $NEST(<script,>))+$INEST(<script,</script)</script*>)+{0,1}

fix the two examples we found. I don't have time to check the Exceptions.ptxt "i_noscr:2" entries yet.