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

Update to work with Web Component v1 Specs #162

Open
itsMattShull opened this issue Dec 1, 2016 · 5 comments
Open

Update to work with Web Component v1 Specs #162

itsMattShull opened this issue Dec 1, 2016 · 5 comments

Comments

@itsMattShull
Copy link

Anyone working on this? I've been using this web component for a while and I'm wanting to update to v1 specs for custom elements and shadow dom. If no one is working on upgrading I'll fork and start a project. If there is already a project I'd love to help migrate.

@jmalonzo
Copy link
Collaborator

jmalonzo commented Dec 1, 2016

None that I'm aware of. Please feel free to fork. Happy to review/merge a PR if you decide to upstream your changes.

@itsMattShull
Copy link
Author

@jmalonzo Here is a repo for v1 compatibility. under the components folder there is app-router. It's in the right format for v1 but when I run gulp watch and it fires up no templates are brought in. I don't get any errors though. Leaving work now. Will look into this later but would appreciate any help looking into the matter. Side note: the HtmlElement javascript error in chrome that you may see is nothing.

@jmalonzo
Copy link
Collaborator

jmalonzo commented Dec 1, 2016

@derekshull Thanks I'll take a look this evening, if not this weekend.

@cliedelt
Copy link

Soo that have been a long weekend?

TypeError: e.registerElement is not a function is being thrown in firefox

@barnomics
Copy link

I did a PR to take care of this issue #170

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

No branches or pull requests

4 participants