You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UI5 DynamicPage(will provide sample link separately) subheading is taking 100% width of the whole header part, while 2.0 version of ui5-webcomponents DynamicPage's subheading is only taking part of header's width.
Raising this issue because our module's design was based on UI5 DynamicPage and we have elements placed in subheading which needs 100% width of header part so they can fit. All of our developments are completed in 2411. But after upgrading to v2.0, our page's style was broken due to this change.
Affected Component
No response
Expected Behaviour
No response
Isolated Example
No response
Steps to Reproduce
...
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
2.3.0
Browser
Chrome
Operating System
macOS Sonoma 14.6.1
Additional Context
No response
Organization
No response
Declaration
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
@summer2200 I assume that you are using UI5 WebComponents for React.
Hello @SAP/ui5-webcomponents-topic-p ,
In UI5 Web Components for React V1, DynamicPage sample uses custom layout, where the subheading takes 100% of page width. Now, In UI5 Web Components for React V2, our DynamicPage is used. In this case, the subheading slot has smaller width. Please check if this is by design. Can be observed here or in UI5 WebComponents for React's Playground .
Bug Description
UI5 DynamicPage(will provide sample link separately) subheading is taking 100% width of the whole header part, while 2.0 version of ui5-webcomponents DynamicPage's subheading is only taking part of header's width.
Raising this issue because our module's design was based on UI5 DynamicPage and we have elements placed in subheading which needs 100% width of header part so they can fit. All of our developments are completed in 2411. But after upgrading to v2.0, our page's style was broken due to this change.
Affected Component
No response
Expected Behaviour
No response
Isolated Example
No response
Steps to Reproduce
...
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
2.3.0
Browser
Chrome
Operating System
macOS Sonoma 14.6.1
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: