Add support in the future for custom elements

[pspeter3]

It would be really cool to allow view to be custom elements. http://coding.smashingmagazine.com/2014/03/04/introduction-to-custom-elements

[mereskin-zz]

+1, that would be nice. I created this PR to prepare a ground for discussion: #1249

[MoOx]

+1 if that's not already doable

[gargantuan]

Custom elements currently work, but are broken in the release candidate. There's a discussion about it here in this issue #4933. it seems the position of the React team is that it will remain broken.

I do not see how web components address any of the issues of modern web development. However, it looks like we will lose all the semnatic goodness of custom elements in support of a spec that's failed before it even begins.

[jimfb]

To be clear: custom elements do work correctly (as intended) in the release candidate. The custom element specification allows for arbitrary attributes to be specified on a custom element, which is why the design decision to use the class attribute instead of className was chosen (the custom elements spec requires us to preserve the full case-sensitive namespace). We will continue the discussion of that topic in the issue you linked.

We have another issue tracking upcoming DOM technology, so I'm going to close this issue out in favor of #2836