-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
DynamicPageHeader expanded automatically on scroll on mobile devices #4129
Comments
Hello @Kalo2412
I guess you need a combination of these two properties. Best Regards! |
@MapTo0 Thank you very much for the answer, unfortunately in landscape mode this property does not make any difference even if set to true (preserveHeaderStateOnScroll). Can you check it? We need this to be always true. |
@MapTo0 ? |
Hey @Kalo2412 I could not reproduce the issue on my side. Best Regards, |
Here is a video that shows the issue: (It is reproduced on landscape mode) |
Hello @Kalo2412 , Regards, |
OpenUI5 version: 1.117.0
Browser/version (+device/version): 'Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.6 Mobile/15E148 Safari/604.1'
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible): https://sapui5.hana.ondemand.com/#/entity/sap.f.DynamicPage/sample/sap.f.sample.DynamicPageWithStickySubheader/code
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
What is the expected result? The header should not be expanded automatically on scroll
What happens instead? The header is internally expanded automatically on scroll
Any other information? (attach screenshot if possible)
https://teamschedule-my.sharepoint.com/:v:/g/personal/mihael_kirov_teamschedule_digital/Eac25tkkwzpPlanvi3NGuoABZGiRSpzccp9959XwNyzDxw?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0NvcHkifX0&e=aprmvL
The text was updated successfully, but these errors were encountered: