| Poll: Why don't you write filters for proxomitron? This poll is closed. |
|||
| I don't know HTML code, neither proxomitron expressions | ![]() ![]() |
7 | 58.33% |
| I don't have ideas for creating filters | ![]() ![]() |
0 | 0% |
| I don't have time for these things | ![]() ![]() |
1 | 8.33% |
| I wrote some filters but didn't post them | ![]() ![]() |
4 | 33.33% |
| With Adblock plus and NoScript (or similars) i don't need anything more | ![]() ![]() |
0 | 0% |
| Total | 12 vote(s) | 100% | |
| * You voted for this item. | [Show Results] |
|
[Poll] Why don't you write filters for proxomitron?
|
|
Nov. 29, 2008, 03:53 PM
Post: #13
|
|||
|
|||
RE: [Poll] Why don't you write filters for proxomitron?
lnminente Wrote:Is very reccomendable the use of $NEST() and $STOP(). I use $NEST quite a bit. However, it can get confused in scripts. I've had problems matching tags in js whether it's a $NESTed match or not. Matching anything in js is a PITA. For this reason, as a test, I am switching some of my html script matching filters to this: Code: <script(\s|>)*</script >This seems to work better than $NEST on html pages. Technically, any </ should signify the end of a script on a html page. In practice, this only seems to hold true when it's a closing script tag. That's why a closing script tag "inside" html js is always obscured. Of course, if it's $TYPE(js) page, all matching bets are off. So far, it's solved some problem matches and not caused any issues. Time will tell. z12 |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help







![[-]](images/ONi/collapse.gif)