Previously, “initializeHost” was called ahead of “addListeners”. There was an edge case where such depth-first initialization made it possible for synchronous events from children to be emitted before the delegated event listeners had been setup on the parent.
This change ensures the following happens in order on first connection:
The host itself is initialized.
The static listeners are added.
The host undergoes its initial render.
Previously, (2) and (3) were conceptually swapped.
Previously, “initializeHost” was called ahead of “addListeners”. There was an edge case where such depth-first initialization made it possible for synchronous events from children to be emitted before the delegated event listeners had been setup on the parent.
This change ensures the following happens in order on first connection:
Previously, (2) and (3) were conceptually swapped.