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
Instead it renders the link inside a element and an empty subnavigation nav.
I suspect this is because in packages/components/src/components/navigation-item/navigation-item.lite.tsx#32 the prop "hasSubNavigation" is set to true by default and only updated onMount. Additionally updateSubNavigationState starts with a check for the existence of "document", which doesn't exist on the server.
This should be corrected by the client side hydration, but because the server rendering injects a subnavigation (with id), the client side updateSubNavigationState checks find a subNavigationSlot and also renders a subnavigation.
Expected Behaviour
DBNavigationItem should not render a subnavigation when none exists 😀
Screenshots
No response
Browser version
None
Add any other context about the problem here.
No response
The text was updated successfully, but these errors were encountered:
Which generators are impacted?
Reproduction case
When using server side rendering (e.g. next.js) the following code
should render a link inside of an <li> item.
Instead it renders the link inside a element and an empty subnavigation nav.

I suspect this is because in packages/components/src/components/navigation-item/navigation-item.lite.tsx#32 the prop "hasSubNavigation" is set to true by default and only updated onMount. Additionally
updateSubNavigationState
starts with a check for the existence of "document", which doesn't exist on the server.This should be corrected by the client side hydration, but because the server rendering injects a subnavigation (with id), the client side
updateSubNavigationState
checks find a subNavigationSlot and also renders a subnavigation.Expected Behaviour
DBNavigationItem should not render a subnavigation when none exists 😀
Screenshots
No response
Browser version
None
Add any other context about the problem here.
No response
The text was updated successfully, but these errors were encountered: