[w3c/webcomponents] Interfaces for web components (#725)

We read a lot that Safari is not going to implement the `is=""` attribute and therefore we are not going to be able to inherit from built-in elements. 
None the less, we are desperately in need of being able to communicate to HTML parsers that our elements behaves like one of the built in elements, for example a form control. 

Has it ever been considered to introduce an `like="input"` attribute?
This would tell the HTML parser that the custom element is supposed to be treated like an element that implements the input-element-interface.
It's then up to the custom element author to implement all the features of the interface and in return browsers would treat it as an `input` element.

Our use-cases for this currently are:

1. Being able to create an `custom-header` element which is accepted by, for example crawlers as a header element.
2. Create form controls which are picked up by the built-in form element and are treated just like other form controls.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/725