This looks to be related to parent.js:74 + the changes in eadbb005.
Since the move to register children on init() instead of on didInsertElement(), children of an already-setup parent are receiving didInsertParent() on init(). This breaks any code in didInsertParent() that relies on the component's rendered element being present.
This looks to be related to parent.js:74 + the changes in eadbb005.
Since the move to register children on
init()
instead of ondidInsertElement()
, children of an already-setup parent are receivingdidInsertParent()
oninit()
. This breaks any code indidInsertParent()
that relies on the component's rendered element being present.