Skip to content

Loading…

Invalid childNodes on previous parent is returned after calling domApi.appendChild #2235

Closed
eeid26 opened this Issue · 2 comments

2 participants

@eeid26

http://jsbin.com/litugehexu/edit?html,console,output

Also the following issue could be a different mutation of the reported issue. Both issue are due to caching the _lightChildren on the parent

After calling domApi(customElement).appendChild(domApi(customElement).nextSibling) and then flush, the nextSibling of the custom element is not reported correctly by domApi.

http://jsbin.com/hijoxawewa/edit?html,console,output

@sorvell sorvell added the p1 label
@sorvell sorvell self-assigned this
@sorvell
Owner

Thanks for the detailed reproductions. Yes, both issues look like the same problem.

@sorvell sorvell added the in progress label
@sorvell sorvell closed this issue from a commit
@sorvell sorvell Fixes #2235. Manages logical information in shady distribution more d…
…irectly by capturing it explicitly when needed and not whenever distribution is run.
21500fb
@sorvell sorvell closed this in 21500fb
@eeid26

Thank you. it's working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.