search

SAP / ui5-webcomponents-react

A wrapper implementation for React of the UI5 Web Components that are compliant with the SAP Fiori User Experience
https://sap.github.io/ui5-webcomponents-react/
Apache License 2.0
426 stars 94 forks source link

[ObjectPage/ObjectPageSection] - onToggleHeaderContent in expanded State when scrolled down add a lot of blank space #4693

Closed Rahishsaifi closed 1 year ago

Rahishsaifi commented 1 year ago

Describe the bug

Object Page w/ long Header Section: Toggled - Expanded State when scrolled down add a lot of blank space

Isolated Example

No response

Reproduction steps

1.Toggle Object Page 2.Ensure Header Section is expanded 3.Scroll Down

Expected Behaviour

Empty screen should not show

Screenshots or Videos

image image

UI5 Web Components for React Version

1.7.3

UI5 Web Components Version

1.9.3

Browser

Chrome, Edge, Firefox, Safari

Operating System

Windows

Additional Context

I have update the version "@ui5/webcomponents": "1.13.0", "@ui5/webcomponents-base": "1.13.0", "@ui5/webcomponents-fiori": "1.13.0", "@ui5/webcomponents-icons": "1.13.0", "@ui5/webcomponents-react": "1.15.1", "@ui5/webcomponents-react-base": "^1.11.0",

now I am getting babel error, and i clear cache and build the project but still issue is persist This was the previous ticket which is closed. https://github.com/SAP/ui5-webcomponents-react/issues/4364

Relevant log output

No response

Declaration

Lukas742 commented 1 year ago

Hi @Rahishsaifi

now I am getting babel error, and i clear cache and build the project but still issue is persist This was the previous ticket which is closed.

Please open another issue for this, preferably with a reproducible example leveraging this codeSandbox as for me no error is shown.

1.Toggle Object Page 2.Ensure Header Section is expanded 3.Scroll Down

I wasn't able to reproduce this behavior anymore (see codeSandbox). Please include a reproducible example and video or detailed steps to reproduce the problem.

github-actions[bot] commented 1 year ago

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Inactive issues will be closed after 7 days. Thanks.

github-actions[bot] commented 1 year ago

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please first check to see if the maintainers have requested additional input and provide it if necessary, or post a detailed description of why this issue is still a problem.