title: Custom input element in native form
body: <p>With web components one of the elements that people want to create and override most is <code>&lt;input&gt;</code>. Input elements are bad because they are many things depending on their type and usually hard to customize, so it's normal that people always want to modify their looks and behavior.  </p>
  
  <p>Two years ago more or less, when I first heard of web components, I was pretty excited and the first kind of elements that came to my mind that I wanted to create were custom input elements. Now that the spec is finished it looks like the need I had for input elements is not solved. Shadow DOM was supposed to allow me to change their internal structure and looks but input elements are blacklisted and can not have a shadow root because they already have a hidden one. If I want add extra logic and behavior, custom, built-in elements with the <code>is</code> attribute should do the trick; I can't do the shadow DOM magic but at least I have this, right? well Safari is not going to implement it, polymer won't use them for that reason which smells like a standard that is going to be deprecated soon.  </p>
  
  <p>So I'm left with normal custom elements; they can use the shadow DOM and have whatever logic I want, but I want them to be inputs! they should work inside a <code>&lt;form&gt;</code>, but if I'm correct, form elements don't like them.  Do I have to write my own custom form element as well that replicates all of what the native one does? Do I have to say goodbye to <code>FormData</code>, validation API, etc? Do I lose the ability to have a form with inputs that works without javascript?</p>