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.

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

Web Components declarative Custom Elements #2557

Closed
6 tasks
jfbrennan opened this issue Mar 15, 2018 · 2 comments
Closed
6 tasks

Web Components declarative Custom Elements #2557

jfbrennan opened this issue Mar 15, 2018 · 2 comments

Comments

@jfbrennan
Copy link

Here's a pretty interesting proposal for Declarative Custom Elements that ought to look familiar to Riot devs:
https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Declarative-Custom-Elements-Strawman.md

I think that reflects well on Riot. Good job!

  1. How would you tag this issue?
  • Question
  • Bug
  • [ X ] Discussion
  • Feature request
  • Tip
  • Enhancement
  • Performance
@ShiMeiWo
Copy link

ShiMeiWo commented May 8, 2018

So interesting. I'll watch the situation.

@GianlucaGuarini
Copy link
Member

I don't like the custom elements specs because they rely heavily on classes inheritance. I made the first custom elements riot implementation here https://github.com/riot/custom-elements and I am really happy with it. I think I will keep it optional also for the new upcoming major release. Thanks for the link anyways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants