You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on integrating the StepperModule into my app and I'm having difficulty getting it to render correctly.
Currently, on page initialization of my component, the Stepper components create 2 copies of themselves while awaiting resolution of the page from the SSR hydration. This causes the content on my page to double-out and look...strange. I've verified that the issue is due to SSR issues by adding ngSkipHydration to the component.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I'm currently working on integrating the StepperModule into my app and I'm having difficulty getting it to render correctly.
Currently, on page initialization of my component, the Stepper components create 2 copies of themselves while awaiting resolution of the page from the SSR hydration. This causes the content on my page to double-out and look...strange. I've verified that the issue is due to SSR issues by adding ngSkipHydration to the component.
Currently, I'm importing the module as
The components are put into the view as
activeTab is just a public number variable on the component class.
The component doesn't have any direct DOM manipulations; everything is going through Angular's libraries.
Is there something I'm missing here.
Beta Was this translation helpful? Give feedback.
All reactions