We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As summarized in https://wiki.whatwg.org/wiki/Custom_Elements#Subclassing_existing_elements, subclassing existing built-in subclasses elements of HTMLElement pose many issues. We should remove this feature (extends on the custom element definition and is content attribute) at least from v1.
HTMLElement
extends
is
The text was updated successfully, but these errors were encountered:
According to the spec using type extension approach is the only way to create renderable components in SVG namespace.
Sorry, something went wrong.
I'm proposing to remove that in v1.
Actually, this is a duplicate of the issue #133.
No branches or pull requests
As summarized in https://wiki.whatwg.org/wiki/Custom_Elements#Subclassing_existing_elements, subclassing existing built-in subclasses elements of
HTMLElement
pose many issues. We should remove this feature (extends
on the custom element definition andis
content attribute) at least from v1.The text was updated successfully, but these errors were encountered: