fix ie7 problem of attribute class vs. className

[luobotang]

No description provided.

[stephenmathieson]

@matthewmueller just changed this for svg support in 2aef7c5.

personally, i'd rather support svg than a super old browser.

[luobotang]

Maybe you are right.
Maybe only a few people like me care about the super old browser.

[matthewmueller]

Yah, I'm -1 unless we can come up with a solution that works for both. This is a heavily depended on module, so there should be no breaking changes at this point.

[luobotang]

I have made a copy of this, 'fix' the IE7 problem then use it in my work. (I know, not a good way to do it)
The SVG support is currently not part of my work, but, I think find a solution for both is a better idea.

[matthewmueller]

Okay :-) I'm going to close this for now. If you find some time to test both, let me know and I'll reopen.

[stephenmathieson]

@luobotang no, forking is what components are all about. There's no reason you shouldn't maintain an IE7-friendly version of this component. Maybe someone else needs IE7 support but doesn't care about SVG. if I were you, I'd push a 2.0.0 tag out and start using your own version ;)

[luobotang]

@stephenmathieson Maybe you're right.
But that's a little 'complicated' & 'confused' for me .... ^_^
Thanks for your reply. Now I know that the className problem is not a simply bug.
@matthewmueller Thank you too, for your suggestion.