-
Notifications
You must be signed in to change notification settings - Fork 94
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
[Form]: Read order in forms is not correct and column layout does not work for groups. #5704
Comments
) When a `Form` contains only `FormItems` and no `FormGroups`, the reading and tab order of the form items should be first top to bottom, then start to end. Part of #5704
) When a `Form` contains only `FormItems` and no `FormGroups`, the reading and tab order of the form items should be first top to bottom, then start to end. Part of #5704
@MarcusNotheis , |
#5824 should fix the column layout if only FormGroups are used. |
🎉 This issue has been resolved in version v1.28.2 🎉 The release is available on v1.28.2 Your semantic-release bot 📦🚀 |
Describe the bug
Hi team,
A couple issues:
Please refer to: https://experience.sap.com/fiori-design-web/form/#top
Isolated Example
Issue 1: https://stackblitz.com/edit/github-pzlhay?file=src%2FApp.tsx
Issue 2: https://stackblitz.com/edit/github-rmcazv?file=src%2FApp.tsx
Reproduction steps
Expected Behaviour
For issue 1, here is an example of the expected behavior from ui5 classic framework. SimpleForm. https://ui5.sap.com/#/entity/sap.ui.layout.form.SimpleForm/sample/sap.ui.layout.sample.SimpleForm_Column_oneGroup234
For issue 2, here is an example of the expected behavior from ui5 classic framework. SimpleForm.
https://ui5.sap.com/#/entity/sap.ui.layout.form.SimpleForm/sample/sap.ui.layout.sample.SimpleForm_Column_twoGroups234
Screenshots or Videos
Issue 1:
Issue 2:
UI5 Web Components for React Version
main
UI5 Web Components Version
main
Browser
Chrome, Edge, Firefox, Safari
Operating System
No response
Additional Context
No response
Relevant log output
No response
Organization
SF
Declaration
The text was updated successfully, but these errors were encountered: