Test your configuration!

[Kye-U]

http://www.kephyr.com/popupkillertest/index.html

My Sidki config, slightly modified for my needs, passed the test with only 2 missed, tests 12 and 21.

I've created filters to remove all examples of those tests

My filter for test 12:

Code:

[Patterns]
Name = "Layer Killer [Kye-U]"
Active = TRUE
URL = "$TYPE(htm)"
Limit = 1512
Match = "<div*STYLE=(\"|\'|)*(position:( |)absolute;|z-index:( |)([0-9]+{1,*}))*(\"|\'|)*</div>"

My filter for test 21:

Code:

[Patterns]
Name = "Remover Sidebar Opener [Kye-U]"
Active = TRUE
URL = "($TYPE(htm)|$TYPE(js))"
Limit = 24
Match = "sidebar.addPanel"
Replace = "Shonenscape"

[Siamesecat]

In the Layer Killer filter, why target "position: absolute"? All that does is position an image in a precise place on the page. The Mozilla browser update site (update.mozilla.org) uses it (at least on the Firefox pages) to position the logo of the browser.
If the window that appears to pop up is prepared in a hidden layer and then suddenly made visible, would it not be better to disable the retrieval of the layer? On that popup test page, before the stuff in the <DIV tags, there are several references to layers in the code.

[JD5000]

Here's a version I've been using.. Seems to be ok.

Tested at...

Carmax
at&t wireless
kephyer.com

It doesn't catch versions encoded with JS tho. (I've never seen one of those in the wild. )

The filter should be safe.. Since any webmaster with basic CSS knowledge, knows that you don't put an ID and a style in the same tag. If your going to use an ID, you put the style info in a external CSS file, or in style tags... Luckily for us... They don't. Also, the filter scans for the size of the DIV, so that should also cut down on erroneous matches..

That being said, I've only tested the filter for a week or so..

Code:

[Patterns]
Name = "Block: Floating Ads {8.d} [test]"
Active = TRUE
URL = "$TYPE(htm)(^$TST(keyword=*.(ads|adfloat).*))"
Bounds = "$NEST(<div,</div>)"
Limit = 4096
Match = "<[^>]++ STYLE=$AV(*absolute*)"
"&"
"<[^>]++ STYLE=$AV(*width: [#300-650]*)"
"&"
"<[^>]++ id=$AV(\2) "
"&"
"<[^>]++ style=("|'|)\0 *"
Replace = "<div id=\0Prox-\2\0 ></div>\r\n"
"<span class=Prox style=\0display:$GET(displayS)\0>"
"<a class=PrxLink title=\0Filter: Block: Floating Ads - \2\0 href=\0\u&keyword(.adfloat.)\0 >[Content Blocked]</a>"
"</span>"

Primitive, but it gets the job done. [smoke]

~JD

[besafe]

With my regular config JD_Advanced_A.cfg and a few other filters, I missed 11,12,19,21.(IE) Added JD's 12 filter and Kye-U's 21 filter and failed 11,19,21. Is there a specific place to put the filter for test 21 for it to work?

What do I need to activate to block the pop-up requesting it be added to favourites?(11)

I will say that when I am surfing for real I rarely ever have a pop-up of any sort with the config I'm using.

Thanks for any replies and also for the config JD and the site Kye-U.

[elshaddai]

I did the test at the kephry site with JD5000 config (previous to alpha) and missed just one....the add to favorite popup.

[JD5000]

Had to update a few things for IE... Next update should cover them all. Not sure about 21 tho... Seems kinda silly to me.. But, what the heck. LOL Oh, and the flash popup is the only one that will get through... Unless you enable the "click to play flash" filter... Heh, I actually forgot the filters name. haha

[Siamesecat]

JD5000,

I like your filter! It tells one immediately that something was blocked, and gets more specific if one runs the cursor over the link. Nice touch.

The name of the filter to turn flash into a link is something like "Flash Animation to Link".

[Kye-U]

From Sidki's Filter-Set:

Code:

[Patterns]
Name = "<object>...: Toggle Flash     3.12.28 [jd s] (d.2)"
Active = TRUE
URL = "($TYPE(htm)|$TYPE(js)|$TYPE(vbs))(^$TST(keyword=*.(flash|code).*))"
Bounds = "<(object*>(*</object >|)|embed*>(*</embed >|)|iframe*>(*</iframe >|))"
Limit = 2048
Match = "(*(shockwave|macromedia|flash|swf)*)\#"
"&(^$TST(pre=1)|$TST(textarea=1))"
""
"&*(src|<param name=$AV(movie) value)="
"$AVQ("
"(\\|)('$SET(7=")|("|)$SET(7='))"
"(([^/?]+/)+([^.?"'\\]+)\3[^"'\\]+)\2*"
")"
""
"&((<(embed|object|iframe)*>&&*width=$AV(\8)*&&*height=$AV(\9)*)|)"
"&($TST(script=*)$SET(1=\\\7)|$SET(1=\7))"
""
"&("
"(^$TST(pflash=*))"
""
"$TYPE(htm)$SET(collect=$GET(collect)"
"<span id="PrxFlashInfo" class="Prox" style="display:$GET(displayI)">"
"&#8593;<a id="PrxFlashInfo" class="Prox" href="javascript:PrxToggle('PrxFlash','id','yes')""
" target="_self">flash</a> </span>"
")"
""
"|)"
"&$SET(pflash=$GET(pflash)$DTM(c))"
Replace = "<span id=PrxFlash class=ProxFlash$GET(pflash) style=display:inline>"
"&#8593;"
"<a id=PrxFlash title=Toggle Flash"
" href=javascript:PrxToggle(\1ProxFlash$GET(pflash)\1,\1cl\1,\1yes\1) target=_self>"
"Flash \8x\9</a>"
"<a id=PrxFlash title=Entire Window href=\2>: \3</a>"
"</span>"
""
"<span id=PrxFlash class=ProxFlash$GET(pflash) style=display:none>"
"\#"
"</span>"

[besafe]

Well who would have thunk? I turned on IE's pop-up stopper along with Proxo and only failed #11.

[sidki3003]

Actually - regarding my config - i don't know yet what to do with test #12 and #21.
Frankly, i don't care much about artificial tests, as long as i don't see them in the wild.
Never came accross #21 - the bookmark thingie, that is.
The real-life #12 examples got blocked by other filters so far (at least for the upcoming config -- mainly because most use setInterval/setTimeout, which gets intercepted now).

sidki

[JD5000]

Small update.

Code:

[Patterns]
Name = "Block: Floating Ads {8.d} [test]"
Active = TRUE
URL = "$TYPE(htm)(^$TST(keyword=*.(ads|adfloat).*))"
Bounds = "$NEST(<div,</div>)"
Limit = 2048
Match = "[^>]++ STYLE=$AV(*absolute*&&*width : [#315-650]*)"
        "&"
        "[^>]++ id=$AV(\2) "
        "&"
        "*<(i[fm]|ob|emb)*"
Replace = "<div id="Prox-\2" ></div>\r\n"
          "<span class=Prox style="display:$GET(displayS)">"
          "<a class=PrxLink title="Filter: Block: Floating Ads - \2" href="\u&keyword(.adfloat.)" >[Content Blocked]</a>"
          "</span>"

[Siamesecat]

JD5000,

Just out of curiosity, why is the second filter better than the first? Both work.

[JD5000]

The second filter will only kill floating DIV's if they contain a img, iframe, embed or object tag. An attempt to cut down on erroneous matches.

[toods]

I am using 'Grypen's 11 Nov. 04' filter pack (essentially JD's Advanced Alpha 14 Oct 04 with Kye-U's Security Pack 4.24). I have not activated any of Kye-U's filters for the first test.

Test result - failed tests 18 and 27.

Are there any filters around to stop these 2 tests?.

Thanks Bill.

[z12]

Hi Bill,

Welcome to the Un-Official Proxomitron Forum.

I'm a bit surprised that your the first one to mention this, since Grypens is basically a "packaged" version of JD's filter set.

With regards to test 27, maybe its new. Anyway, it looks like this filter was designed to catch things like that:

Code:

Name = "Kill (some) window.external methods          [k]"
Active = TRUE
URL = "($TYPE(htm)|$TYPE(js)|$TYPE(vbs)|$TYPE(oth))(^$TST(keyword=*.(js|jsprop).*))"
Limit = 80
Match = "window.(parent.|)external."
"(AddChannel|AddDesktopComponent|AddFavorite|"
"AutoScan|ImportExportFavorites|IsSubscribed|NavigateAndFind|ShowBrowserUI)\0[^(]+"
"&"
"$SET(match=$GET(match) Kill (some) window.external methods  - \0<br />)"
Replace = "null; "

The first line of the match expression needs to be changed like so:

Code:

Match = "external."

As far as test 18 goes, I don't think thats a new test. The script they are using generates an error with firefox, so perhaps this is another ie based browser issue. It seems to me I read something about this somewhere, but I can't remember where. Maybe theres a windows update that fixes this.

Mike