className prop not working with custom DOM elements in 0.14.0-rc1

The className prop does not appear to get mapped correctly when applied to custom DOM elements in 0.14.0-rc1.

JSFiddle: https://jsfiddle.net/hellosmithy/5pdujnfq/1/

[syranide]

It works if you set class instead.

cc @jimfb perhaps? (#3067 is related I assume)

[mikeybox]

@jimfb what we’re already seeing is that the change between standard DOM elements and custom element behaviour is counter intuitive and thats the point being made. You’d assume currently that using className would output class because thats what happens everywhere else. Suddenly the behaviour changes because of a dash in the element name which is arbitrary. You’re assuming that the use of a dash means I want to create a web component that is going to have special handling of attributes. It’s currently counter intuitive which is why it keeps going around in circles. It seems like the extensive whitelisting is a result of the behaviour change added to custom elements where all props are mapped.

It’s clear we all care about this stuff because react is probably the coolest framework around and we use it every day. So yeah people are going to get passionate about it because its so important. Whats important especially to us is the use of custom elements as standard html elements using the current 0.13 behaviour that had no prejudice between elements. All were equal. What we’re saying is that the non-equality proposed should be done using a setAttr rather than the current behaviour forking which seems wrong.