|
WISI-NOT-WIG
|
|
Jan. 09, 2009, 08:14 PM
Post: #1
|
|||
|
|||
|
WISI-NOT-WIG
Gang;
OK, I've gotten to the point where I have to admit to needing help on this one - I'm literally ![]() I've decided to let Youtube display flash files. So I disabled the one filter that was preventing flash from running, shown here: Code: Name = "Flash animation killer"(From Scott's default.cfg, I've only turned on Multi.) With this filter manually disbled, Youtube videos display properly. (Note that my on-Load=Load-Off filter is still enabled.) But I now have two problems, to wit: 1) In attempting to make this filter work for all other sites, but to prevent it from working on Youtube, I diddled with the URL field. I thought it'd be simple to negate matching on youtube's URL, like so: Code: URL = "^[^/]++youtube.com/"But that does NOT work! I can use it successfully in other filters, like so: Code: Name = "iFrame/iLayer to link"(Again, I slighly modified one of Scott's default filters.) Note the URL negation...... it works - I need the iframe on the fastmail website in order to do certain things, but I don't want to see them on any other site. But when I do this for Youtube, it doesn't work. Doing the dbug.. thing, and viewing the contents of all the d/l'ed javascript files reveals no other sites being called (except xyz.ytimg.com, essentially the same thing as Youtube). Which brings up Point Number...2) What I See Is Not What I Get!!!! The Scenario: My first line of attack is always to look at the log window, to get the names of which filters have fired. I see that the flash animation killer has fired, so all's well, right? Wrong! I now do a dbug.. on the page (absolutely any Youtube video), and I should see, in red, all the filters that fired, eh? Nope, doesn't happen. No identification of the aforementioned filter, none at all. My question shouldn't need stating, but I'll ask it anyway - how in tarnation can that happen???? The filter fired, but not on the page being displayed? I find that hard to believe, don't you? The Back Story: I've checked the contents of every javascript file from Youtube, nothing there that looks culpable.... The onload event is not allowed to run, but that doesn't matter, the video plays if the filter is manually disabled. The page doesn't obfuscate the Flash player code, in fact it's all spelled out nice and neat, except for the part where it's called - at the exact spot in the code where it would have to be located, all that's present is the warning "You either have javascript turned off, or you need the latest version of Flash Player", yadda yadda. No, I don't have scripting turned off, and yes I do have the latest version of the player. But get this - if I do a dbug.. on either version of the page, I see the same code, no matter if the video can play or not (no matter if the filter is enabled or not). Let me repeat that - the page code does not change, regardless of the filter's state. (And yes, you really should know me well enough by now to not have to ask "did you clear your cache?", etc.) So now I'm really confused/upset/Alzheimered..... how can a filter fire, but not fire? This is absolutely the first time I've ever heard of such a thing, let alone experienced it personally. And to complete the conundrum, how come the URL negation doesn't work? I know for a fact that all the pertinent server calls are on Youtube's site (or xyz.ytimg.com, the same thing), there're no hidden 3rd party sites being called, so far as I can see. Anyone got any ideas I haven't brought out? Thanks. Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
|
Jan. 09, 2009, 08:42 PM
Post: #2
|
|||
|
|||
|
RE: WISI-NOT-WIG
does Proxo's "recent URL" list show any URL's that are loading a .js file, you can't block the object/embed within that URL's .js...
|
|||
|
Jan. 11, 2009, 07:42 AM
Post: #3
|
|||
|
|||
|
RE: WISI-NOT-WIG
ProxRocks;
(Jan. 09, 2009 08:42 PM)ProxRocks Wrote: does Proxo's "recent URL" list show any URL's that are loading a .js file, you can't block the object/embed within that URL's .js...I double-checked, there are no js files stored anywhere on my 'puter, so I can't look inside. I note that the page source code calls for at least one, possibly two, js files to be loaded from the server. The log window says this happens (response: OK), but they're nowhere to be found. Strange, no? ![]() What you say my have more than a grain of truth in it, it'd be nice if this were the problem. Alas, 'tis not to be..... checking it out, that is. I'll keep looking though, thanks. Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
|
Jan. 11, 2009, 11:20 PM
Post: #4
|
|||
|
|||
|
RE: WISI-NOT-WIG
it's been my experience that many .swf's actually have their object/embed tags within a .js and not within the web pages actual source code...
i'm not sure if the .js files are "session only" or not, but if you go to a site where you're having flash problems, i highly suspect the site is "fetching" a .js from a different domain... so your URL's "not match" will have to match that domain also... |
|||
|
Jan. 13, 2009, 05:17 AM
Post: #5
|
|||
|
|||
RE: WISI-NOT-WIG
(Jan. 11, 2009 11:20 PM)ProxRocks Wrote: it's been my experience that many .swf's actually have their object/embed tags within a .js....Give that man a big see-gar! It was a js file from ytimg.com, a subsidiary of youtube. Haven't looked at it, because it doesn't actually load into my browser's cache, but once I saw the name in the "Proxo thinks" list, I decided 'what the heck', and just wrote the negation for that URL instead. Works like a charm. Now to see what happens with beaucoup other sites that are about to be swept out with the trash. (Actually, they only got in when I would forget to manually disable the filter. )Mucho gracias! Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help




Doing the dbug.. thing, and viewing the contents of all the d/l'ed javascript files reveals no other sites being called (except 

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

(Actually, they only got in when I would forget to manually disable the filter.