John Jenkins

> Do we have any angular dev's here who have some insights into change detection etc? The regular task queue uses requestAnimationFrame which works like desired. @gratzl-dev maybe?

@danielleroux did you try adjusting the [taskQueue](https://stenciljs.com/docs/config#taskqueue) option before your PR? It is (or was?) async, perhaps you just wanted `immediate` and we can revert? idk - haven't looked much...

@danielleroux / @mamillastre - I've just noticed this hidden in Stencil's docs too ... > /** > * When a component is first attached to the DOM, this setting will...

I've just tried this out and `initializeNextTick` does indeed seem to fix this issue in Angular. The main issue with that however, is that `initializeNextTick` doesn't propagate within the `dist-custom-elements`...

> While setting the initializeNextTick works it would be equal for all builds and components alike, it would be better if it could be turned on/off for different output targets...

> Seems more like a workaround, would it not be better to have a flag in the @Component decorator that better captures the intent Perhaps? However I'd prefer for Stencil...

awesome - thanks for the investigation @kristilw

yep @mamillastre - re-opened

however - this particular issue / repro is fixed or rather has consistent workarounds now. per component: ```ts async componentWillLoad() { return new Promise((resolve) => { requestAnimationFrame(() => { console.log('componentWillLoad',...

> Even with the workarounds, I think that this is still a breaking change between the 4.35 and 4.36 versions. The change between those versions is Stencil got much faster...