Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Disallow extension of subclasses of HTMLElement and SVGElement/MathMLElement #363

Closed
rniwa opened this issue Jan 23, 2016 · 3 comments
Closed

Disallow extension of subclasses of HTMLElement and SVGElement/MathMLElement #363

rniwa opened this issue Jan 23, 2016 · 3 comments
Labels
custom-elements v1

Comments

@rniwa
Copy link
Collaborator

rniwa commented Jan 23, 2016

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.
@jarek-foksa
Copy link

According to the spec using type extension approach is the only way to create renderable components in SVG namespace.

@rniwa
Copy link
Collaborator Author

rniwa commented Feb 6, 2016

According to the spec using type extension approach is the only way to create renderable components in SVG namespace.

I'm proposing to remove that in v1.

@rniwa rniwa added the v1 label Feb 6, 2016
@rniwa
Copy link
Collaborator Author

rniwa commented Mar 1, 2016

Actually, this is a duplicate of the issue #133.

@rniwa rniwa closed this as completed Mar 1, 2016
@rniwa rniwa mentioned this issue Apr 30, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
custom-elements v1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jarek-foksa @rniwa