> We share custody over the bratty toddler — custom elements. Now that Apple has declared veto against the `is` attribute, I think the author should be prepare

> We share custody over the bratty toddler — custom elements. Now that Apple has declared veto against the `is` attribute, I think the author should be prepared to give up on that claim. <input is="my-fancy-input" type="text"/> This will not work. To assign behavior to the input via Custom Elements, your only remaining option is to create a whole new element. <my-fancy-input/> This might append a normal `input` element to the Shadow DOM, but still won't make the form accessible or even just behave naturally without substantal over-engineering. Custom Elements have become a cause the major concern identified by the article. > Recreating browser features will almost always be both under- and over-engineered. This problem is identified in the Custom Elements specification already [1] so the browser vendors are simply not with us here. [1] http://w3c.github.io/webcomponents/spec/custom/#custom-elements-autonomous-drawbacks http://w3c.github.io/webcomponents/spec/custom/#custom-eleme...