-
Notifications
You must be signed in to change notification settings - Fork 275
[FlexibleColumnLayout | ui5/webcomponents-react | v2.10.0]: Incorrect class and attribute for first column #11545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @KonradPietocha please provide a link for testing |
Hello @Lukas742 could you take over? |
We wanted to update kyma/busola to ui5 v2.10, but my PR has this exact bug, so for now we can't upgrade to this version and the PR is blocked. |
@KonradPietocha we need an isolated sample of the issue. You can use this stackblitz sample, created by us. You can choose the ui5-webcomponents version in the "dependency panel", |
the behavior is reproducible in your docs example, so this is not an issue with our wrapper but the component. Steps to reproduce the issue:
2025-05-19_15-23-42.mp4 |
Yes. @LidiyaGeorgieva Here you can also reproduce my case in the middle column by quickly clicking the "Enter full screen" button |
Hello @SAP/ui5-webcomponents-topic-p please have a look at this issue. Steps to reproduce:
Best Regards, |
This issue has been closed. To reopen, just leave a comment! |
Bug Description
Describe the bug
When we quickly change (during tests) the layout from "TwoColumnsMidExpanded" to "MidColumnFullScreen" and so on, at some point the first column stays forever with the class "ui5-fcl-column--hidden" and remains invisible even in the case of "TwoColumnsMidExpanded" and "OneColumn" (empty).
Affected Component
FlexibleComponent
Expected Behaviour
Fist column should be visible in case "TwoColumnsMidExpanded" and "OneColumn".
Isolated Example
No response
Steps to Reproduce
Log Output, Stack Trace or Screenshots
Priority
None
UI5 Web Components Version
2.10.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
SAP
Declaration
The text was updated successfully, but these errors were encountered: