Skip to content

Conversation

@LidiyaGeorgieva
Copy link
Contributor

The behaviour in the documentation page
https://ui5.github.io/webcomponents/nightly/components/fiori/NavigationLayout/
show that sometimes initially the window.innerWidth is 0.
This breaks the responsiveness logic.
To fix it I added check of the the screen width again when calculating the collapsed state.

…ting the collapsed state

The behaviour in the documentation page
https://ui5.github.io/webcomponents/nightly/components/fiori/NavigationLayout/
 show that sometimes initially the window.innerWidth is 0.
This breaks the responsiveness logic. To fix it I added check of the the screen width
again when calculating the collapsed state.
@ui5-webcomponents-bot
Copy link
Collaborator

ui5-webcomponents-bot commented Jan 8, 2026

🧹 Preview deployment cleaned up: https://pr-12877--ui5-webcomponents.netlify.app

@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview January 8, 2026 15:30 Inactive
Copy link

@Stoev Stoev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rephrase the commit header, but this is a superficial change, the current one is also fine:

fix(ui5-navigation-layout): recheck the screen width upon calculating the collapsed state #12877

@LidiyaGeorgieva LidiyaGeorgieva changed the title fix(ui5-navigation-layout): check the screen width again when calculating the collapsed state fix(ui5-navigation-layout): recheck the screen width upon calculating the collapsed state Jan 9, 2026
@LidiyaGeorgieva LidiyaGeorgieva merged commit eb58a0a into main Jan 9, 2026
14 checks passed
@LidiyaGeorgieva LidiyaGeorgieva deleted the NavLayoutFix branch January 9, 2026 13:22
@ui5-webcomponents-bot ui5-webcomponents-bot temporarily deployed to preview January 9, 2026 13:22 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants