custom elements, as implied in lower-case-convention.md, not working

[pekim]

As I understand lower-case-convention.md, custom element names are now supported.

However when I try to do this (using 0.12.0), following the example in the gist, the jsx fails to be transformed.

var component = React.createClass();
return <component />;

Error: Lower case component names (component) are no longer supported in JSX: See http://fb.me/react-jsx-lower-case
    at Array.visitReactTag [as 0] (/home/mike/hipcac2/node_modules/react-tools/vendor/fbtransform/transforms/react.js:66:13)

What am I misunderstanding, or doing wrong. Or is that gist misleading?

[zpao]

component was an example there. It was being used to indicate that if there were an HTML tag called component then React would use that, not your custom component.

Currently in the JSX transform we still check a whitelist of known HTML elements. We won't be doing that in the future, so 0.12 is a release that allows you to upgrade without breaking in completely mysterious ways. Eg, here we break at compile time so you don't ship code like this to production.

[pekim]

So the intention is that in a future version the whitelist will not be checked, and we'll be able to render custom elements at will? At least that's what I'm hoping.

In my case I want to be able to render a webview tag, which is likely a little too obscure to warrant being whitelisted.

[zpao]

Correct. And yea, I wouldn't add webview to the whitelist anyway. Not because it's obscure but because it's a non-standard tag.

[waldreiter]

Support for <webview> was requested here: #2108

[zpao]

As I was closing that issue I noted that you could use React.createElement('webview') directly. However it's not available on React.DOM or as part of the JSX transform.

[pekim]

For now I'm using dangerouslySetInnerHTML as a workaround .