-
Notifications
You must be signed in to change notification settings - Fork 12
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
UI column width issue using Fiori elements #1
Comments
Hello @w48402, With newer UI5 versions there is a gap between the last column and the end of the screen, similar to the screenshot you provided. This repo is relatively old, so the table occupies the entire width of the screen. |
Thank you Miyasuta for your quick response. How can i fix this issue then? or should I go with fiori free style rather than hardcoding the width in fiori elements. Any suggestions or guidance how to go ahead. Thanks, |
@w48402 |
Thank you. I totally agree with you but table with less columns like mine won't be giving good user experience due to this gap between the last column and end of the screen. How to fix this. Sorry for asking so many questions, I am relatively new in Fiori area, hence troubleshooting. |
Is your app running on BTP Launchpad? Which OData version are you using? |
Yes its running on BTP, I am doing side by side implementation using CAP and fiori odatamodel V2 |
@w48402 You can specify UI5 version in manifest.json with parameter So, if you specify a UI5 version lower than 1.87, the table would take up the whole screen width. |
Hello Mio,
I am going through your blog and creating CAP application using FIORI elements. I have noticed one thing which i would like to hightlight that columns are not alighing as per their width. So there is mismatch of column width, I have tried to adjust using UI html annotation but its hardcoding and if select more columns then table columns width will be messed up.
I am attaching herewith my sample screenshot. I have noticed that yours column width is perfect. Could you please advise anything you have done anyting for this.
The text was updated successfully, but these errors were encountered: