Preserved Topic: dirty test for MS filters (Page 1 of 1)

Hey all I'm doing a quick little proof of concept on a menu system and I'd like to show what can be done using the MS 5.5+ filters.

Being to lazy to write a complete browser check and I was figuring it would be easier to query the browser whether is accepts filters but I can't figure out the context.

You know something like

hasFilters = (document.filters) 1:0;

anyone know if this can be done?



:[ Computers let you make more mistakes faster than any other invention in human history, with the possible exceptions of handguns and tequila. ]:

Hmm, that sounds exactly correct, have you tried that line of code? Looks like it would work just as you hoped. (I learned from the old "poke & hope" school of programming, heh.)

Your pal, -doc-

Also try document.body.filters

I might be missing something but I'm not sure why you need to. Is it to stop the browser wasting its time or to stop errors being generated? I've had a play with filters and not experienced any cross browser problems as it degrades well into other browsers.

Anyway I'm looking forward to seeing what you've got up your metaphorical sleeve and it might inspire me to brush off some of the stupid things I was doing with filters and look at them in a fresh light.

Emps

Emps, the thing here is that I'm writing a dedicated script that just makes a layer appear and disappear, that's it. Being able to detect whether the browser supports a feature I want to use is much easier/efficient than just finding out which browser, OS etc work and then detecting there.

It's the same as Doc said in another post about the way most of us here detect browsers. We tend to use the nn = (document.layers) ? 1:0; dom = (document.getElementById) 1:0; as opposed to parsing the navigator.appVersion string, knowing what something supports is better than knowing what it is.



:[ Computers let you make more mistakes faster than any other invention in human history, with the possible exceptions of handguns and tequila. ]: