-
Notifications
You must be signed in to change notification settings - Fork 104
ObjectPageHeader: Impossible to make FullWidth Custom Header #7025
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
Any update on this ticket? This will be an important thing to fix and seems like it should be simple to detect that we do not have an image property set on the ObjectPage and so the grid position should be adjusted for the header item to not save space for the image when the image (aka the avatar) is not used. |
🎉 This issue has been resolved in version v2.8.1 🎉 The release is available on v2.8.1 Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version v1.29.19 🎉 The release is available on v1.29.19 Your semantic-release bot 📦🚀 |
Describe the bug
We are using the
<ObjectPageHeader>
component with only one thing inside. The content does not take full width and there is an unexplained space on the right hand side of the screen which becomes much more obvious on a mobile device. The ObjectPageHeader does not pass in any avatar component, but it appears the styles for the content portion are assuming that there must be an avatar.Isolated Example
https://stackblitz.com/edit/github-r35bfcyv?file=src%2FApp.tsx
Reproduction steps
Go the stackblitz example https://stackblitz.com/edit/github-r35bfcyv?file=src%2FApp.tsx
Actual Behavior:
The content in the header is taking most of the screen with a significant right side padding due to the grid CSS.
Expected Behaviour
The content in the header (which has no avatar) should expand full width
Screenshots or Videos
UI5 Web Components for React Version
2.7.2
UI5 Web Components Version
2.7.3
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
Organization
SuccessFactors
Declaration
The text was updated successfully, but these errors were encountered: