I agree modernizr is a different solution. With modernizr you cannot tell easily what browser is being used. It just tells you what is supported and what isn’t but in a generic way. For example something like .box-model in modernizr means that box-model is supported, but you dont know if that means you are in Webkit or FireFox, which both implement the box model a bit differently(this is actually my problem).

With this library isStyleSupported you can check specifically for -moz-box-orient or -webkit-box-orient this will let you know EXACTLY what browser you are and which implementation of box model you are working with.

Of course if it is an older browsers this method won’t work but im not supporting old browsers so that is ok with me.

I have seen Modernizr, the important difference between it and my solution is that my solution has the ability to determine support for any styles you provide the method as opposed to Modernizr’s select few.

Also, my solution is capable of determining support for assignable style values.

Have you seen Modernizr? It’s a library that does, well, precisely this kinda stuff

http://www.modernizr.com/

(I know, this seems spammy, but it seems to me like you could save some time and effort here… )

The only problem with your implementation is that the replace method of strings do not support a function as a second parameter in Safari 2.0.2.

String.prototype.camelcase = function()
{
return this
.toString()
.toLowerCase()
.replace(/(-|\.|\s)(\w)/g, function(a,b,c)
{
return c.toUpperCase();
}) ;
}

console.log( ‘ www-xxx.yyy zzz’)

The test page is correct, IE7 only supports opacity through the use of filters. The opacity property is not supported in any version of IE. See here: http://www.quirksmode.org/css/opacity.html

The camel case method was added solely for syntactic sugar but your absolutely right, that is all it is really good for. I feel the real mistake (in the animation library) is the requirement to use hyphenated styles such as background-color. I’ll be sure to fix that in the next version due out later this month.

As for typeof undefined, I was aware of both points you brought up but I suppose I got a little caught up in my strict type checking to put two and two together.

What you recommended reminds me of the window["undefined"] = window["undefined"] hack (although I’m not sure if its appropriate to call it a hack). Actually, I’ve recently started to use the “in” operator to perform checks against undefined values, (“prop” in cache).

To the point of writing my own library; I have considered it but ultimately felt there was nothing I could offer somebody else hasn’t already.

Not to mention I am under the belief that every project deserves its own library; it would be a bit hypocritical of me to release my own. This belief and my eagerness to get involved in the open source community brought me to one of the few voids in the community; standalone and lightweight modules. I already plan on releasing a whole slew of modules in the future.

Great job on the library too! Glad my animation library served you well.

Thanks!

There are some minor things that I want to point out. Both philosophically and coding-wise.

Philosophically: the camelCase function is evil, it’s more evil when you use getStyle and setStyle inside an animation loop. I would prefer to educate coders in the documentation to camelCase their CSS properties. I realized that when looking at your animation library.

Coding-wise: typeof xxx === “undefined”;
1. Typeof always return strings, strict === is not needed, and the performance penalty is minimal, and I don’t follow my own advice.

2. Munging undefine is faster than using typeof

var undefined; // no values associated
xxx === undefined; // returns true if xxx is undefined

Looking at some of your previous posts, I am wondering why you did not create a complete DOM library since I think you have enough knowledge to do so.

Oh BTW, I gained some insights into DOM animation through the understanding of how your animation library works. I made a library out of that it’s hosted at github.

http://github.com/kltan/short/tree/2d4fb83712aaf76ecaf9dfd1c0ad43fcef9e168f/source

Have a nice day.