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

Auto-registration of polymer-elements broken? #221

Closed
JanMiksovsky opened this issue Jul 26, 2013 · 5 comments
Closed

Auto-registration of polymer-elements broken? #221

JanMiksovsky opened this issue Jul 26, 2013 · 5 comments

Comments

@JanMiksovsky
Copy link

The polymer-all commit e48bc25c537b2353023ec4f4c2e2b10496ce2d05 seems to have broken auto-registration of custom elements defined with <polymer-element>. Elements without a script that explicitly calls Polymer(...) appear to no longer get recognized.

Was auto-registration intentionally rolled back?

@ebidel
Copy link
Contributor

ebidel commented Jul 26, 2013

According to 9a0879f, it looks like you can now add a noscript attribute to the <polymer-element> definition.

@JanMiksovsky
Copy link
Author

Eric: That was it. Thanks.

@sorvell
Copy link
Contributor

sorvell commented Aug 2, 2013

We've temporarily removed the ability to declaratively register a custom element without script. We're currently refining the design of declarative custom elements in polymer such that it works well with native implementations of custom elements and HTML imports.

@ebidel
Copy link
Contributor

ebidel commented Sep 9, 2013

This is back in action, correct? Can we close it?

@sorvell
Copy link
Contributor

sorvell commented Sep 9, 2013

Yes, noscript is back and should be working now, closing.

@sorvell sorvell closed this as completed Sep 9, 2013
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