support custom elements that inherit from native elements about incremental-dom

[sparhami]

It is definitely something I'd like to look into. From what I gathered from this post, it seems somewhat uncertain whether or not is="" will be a part of the final spec. I'd like to wait a bit more and see which way things go.

[rkusa]

Ok, thanks for having a look. I am fine with closing the issue until there are more precise information about the final spec.

[treshugart]

An up to date and curated list of the contentious bits can be found here. Seems to be in the same state.

[sparhami]

Will close the issue for now. We can re-open it if the custom element inheritance ever does become a part of the spec.

[treshugart]

@sparhami this has landed in the spec as "customised built-in elements" (used to be "type extensions"). See: http://w3c.github.io/webcomponents/spec/custom/#custom-elements-customized-builtin-example. As far as I can tell from following the discussions over the past few months, supporting these is something that is being done for v1 and is no longer contentious.

[sparhami]

Looks like that section is still marked as non-normative. Currently, Chrome still uses the document.createElement('button', 'x-foo') syntax. Probably doesn't make sense to implement until at least two browsers have implementations.