In some cases the addedToStage event will fire twice, with a single removedFromStage inbetween, when it initializes. Happens for popups and components within scroll panes. Look if there is a way to automatically detect this pattern and prevent that the component is added and removed from the Context multiple times.

Also consider adding a priority to the listener for the addedToStage event, making it execute later so that ContextBuilders that also rely on addedToStage execute first. Otherwise there is the danger of race conditions.

Alternatively this improvement may be added to the ViewManager directly instead of the Configure tag. May be implemented with a collaborator (ViewInitializationObserver).