jQuery Forum

className already works. I don't plan on providing any other mappings besides class (with quotes) and className (any others are just cryptic and unexplainable).

Ah, I didn't realize className also works. Makes sense that it would. Very cool!

I understand your point, but it is not just 2 letters extra. It is in fact the only standard attribute that needs quotes when in object creation. Or at least probably the most commonly used. Every other attricute we use in the attributes object can be written without quotes and that is what. That was my point. It's not as much about the extra 2 characters but merely consistency. I only blame those guys who wrote the ECMAScript standard.

There should be no complications when reserved words were used like

1. {
2.     class : 'names',
3.     in : 'here',
4.     for : 'anything',
5.     if : 'required'
6. }

But it is not valid javascript unfortunately. And let's bury that topic as there will be no change.

-- Aivo --

True.
It might not be such a bad idea to use quotes tho, since proper JSON requires it. Might aswell make it a general rule.

A JavaScript object is not JSON. JSON describes how to send JavaScript objects/arrays, etc as a string which can then be decoded on the other end.