-
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
Templatizer - exception when notifying two-way binding #3196
Comments
I've bumped into this again and after some more digging, I've found that this problem occurs only when a templatized template is inserted to DOM outside a Polymer element. For example this will work fine:
but this will not (assuming
The problem also doesn't occur if the templatized templates are created to another custom element's DOM, which is how I use them. |
Okay, I think I got it. The error is thrown on this line, because It is only ever set while annotations are being processed during element registration. With any ad-hoc template (also added to Light DOM inside Polymer element), that routine is never called. The call tree is Would it be possible to ensure templatized templates are similarly processed when they are first used to ensure annotations are processed? |
Hi. Is there any chance for a fix? Or any ideas for a possible hack? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
Hi. I've created a sample plunk as an example of using Templatizer. I added two-way binding and it works, but the console logs message
TypeError: Cannot use 'in' operator to search for '{prop}' in undefined
. Do I somehow use Templatizer the wrong way?The text was updated successfully, but these errors were encountered: