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

In shady dom + observeNodes, the disconnect throws #4049

Closed
notwaldorf opened this issue Oct 6, 2016 · 2 comments
Closed

In shady dom + observeNodes, the disconnect throws #4049

notwaldorf opened this issue Oct 6, 2016 · 2 comments
Assignees

Comments

@notwaldorf
Copy link
Contributor

If I use observeNodes to observe a local child, the disconnect bit throws:

screen shot 2016-10-06 at 12 55 19

@mkazlauskas
Copy link

Here are some hopefully helpful insights on iron-input:

  • It throws because observeNodes triggers detached, I believe it shouldn't
  • It doesn't throw if you move observeNodes from attached to ready callback
  • It doesn't throw if you don't use a container like paper-input-container, or if that container doesn't have a <template>

@sorvell
Copy link
Contributor

sorvell commented Oct 28, 2016

Fixed via #4112.

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

4 participants