-
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
Auto binding template not stamped when async import is used to load polymer #1968
Comments
Current workaround:
|
It looks like this only occurs on Chrome when WebComponents polyfill ( ok: http://jsbin.com/cahuha/1/edit?html,output |
Yep confirmed. I'm dynamically loading the polyfill based on feature detection, which means Chrome is never getting it. Confirmed your bins too. |
Thanks. There is an easy fix that will get the The reason that Our typical strategy is to simply wait for HTMLImports to resolve before stamping the We could simply not provide any help for this situation when async imports are used (always stamp if the dom-bind is created after document.readyState === 'complete'. This is the easy fix). Alternatively, we can attempt to see if any currently existing imports are loaded and wait for them to load if not. Unfortunately, HTML Imports currently gives no way to distinguish that an import has already 404'd. In that case this strategy would fail. Another option is simply to make users stamp the |
I'd be happy with a public method for stamping. I suppose if someone is already going the async route, they're probably comfortable/interested in full control. |
Closed via #2090. The |
If one makes their main page import that loads polymer.html async, e.g.
<link rel="import" href="elements.html" async>
, auto binding templates on the page do not stamp their content.The text was updated successfully, but these errors were encountered: