> The double bang will convert to false with the same rules as the > bitwise OR, as I recall.
You're right, I just threw the || in at the last minute to show the two states. (I also left garbage, since there's a div that isn't destroyed.) > @Arain and Sanford: > Why do you recommend checking for the css gradient support over the > browser version? I figured you had some reason to avoid the Navigator object, otherwise that would give you the granular version straight away. Direct detection of the feature you're targeting seemed like the way to go (as opposed to detecting onhashchange, which amounts to browser detection since that isn't the function you're actually looking to use). Then again, I don't think there's a standard that says that a browser can't store and return a given style in script even if it can't yet render it. Me, I've been bitten by a few CSS3 features that would have been detected using this or any other "intelligent" method, but whose implementation was broken (some FF3 and Saf3 bugs, if memory serves). The only way to deal with that stuff is to do flat-out browser detection to render without the broken features even when they appear to be present. -- S.
