-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[0.8] Polymer.import missing #1248
Comments
I've copied the code from 0.5 to https://github.com/TangereJs/Polymer-import/tree/0.8-preview and it seems to work after a minor change. Is this the right approach? It works for my current use case, but it seems to easy ... |
Does anybody have any information about the future of Polymer.import()? Unfortunately that feature is quite essential for us. The version we made at https://github.com/TangereJs/Polymer-import/tree/0.8-preview has an issue when used with FF/IE: in the freshly imported elements the dom-module is sometimes empty. It seems that the dom-module is upgraded after the Polymer() was already executed. As a workaround it works if the Polymer() code is included in the dom-module, so if the code is like
Polymer.import seems to work in IE/FF as well. |
@sorvell Can you comment? I believe there is an importHref instance method, but I'm not sure whether it's a replacement for Polymer.import. |
I've tested importHref it only imports one element and not an array of elements. We can probably work around that limit in our own code. But importHref has the same problem I faced with our port of Polymer.import: nested dom-modules fail to load correctly in IE/FF. importHref works in IE/FF when I move the Should importHref work in IE/FF ? Is this a known problem/bug? |
I've created a new issue to show the importHref issue in FF/IE11 #1343 |
Any help with polymer component imports? Are we doing something wrong or is it really not possible in 0.8 to import components in FF and IE11 ? |
We're investigating a fix for this issue. It stems from limitations of the HTMLImports and CustomElements polyfills. |
Thank you for the feedback, good to know that a fix is coming. |
@sorvell Thanks I also want to know the fix. |
Closing this since #1343 has been fixed. The |
It seems that Polymer.import is missing in 0.8. Polymer.import is also not mentioned in the Migration Notes of the primer.
Are there any plans to bring it back? Is there any new way to load components on demand?
The text was updated successfully, but these errors were encountered: