SAP / openui5

OpenUI5 lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice.
http://openui5.org
Apache License 2.0
2.95k stars 1.24k forks source link

Header of sap.f.DynamicPage with Icon Tab Bar as stickySubheaderProvider jumps when scrolling #4000

Open ChristianBpm opened 6 months ago

ChristianBpm commented 6 months ago

OpenUI5 SAPUI5 version: 1.71.64

Browser/version (+device/version): Chrome 121.0.6167.86

Any other tested browsers/devices(OK/FAIL): Firefox 122.0 (FAIL) / Edge 122.0.2365.80 (FAIL)

URL (minimal example if possible): https://sapui5.hana.ondemand.com/1.71.64/#/entity/sap.f.DynamicPage/sample/sap.f.sample.DynamicPageWithStickySubheader

User/password (if required and possible - do not post any confidential information here): -

Steps to reproduce the problem:

  1. Open URL
  2. Pin the head area
  3. Scroll down
  4. Scroll up

What is the expected result? No jumping of the header

What happens instead? Jumping of the header

Any other information? (attach screenshot if possible)

We use a Dynamic Page with an Icon Tab Bar as stickySubheaderProvider and a Responsive Table in there. Since using SAPUI5 version 1.71.64, a transparent area briefly jumps in the header (in the large rectangle in the screenshot) when you scroll up the page. This only happens when the head area is pinned. With fitContent="true" in the Dynamic Page it no longer jumps, but the HeaderToolbar of the Responsive Table is no longer sticky (or is hidden by the Icon Tab Bar) when scrolling down despite sticky="ColumnHeaders,HeaderToolbar". In addition, the HeaderToolbar jumps (in the small rectangle in the screenshot) a bit when scrolling down if the header is set as sticky.

The exact same problem can also be reproduced in the official documentation at the URL given above.

In version 1.71.50 everything still works correctly.

BlinkInTheHeader2

ndeshev commented 6 months ago

Hello @ChristianBpm , Thank you for sharing this finding. I've created an internal incident DINC0094823. The status of the issue will be updated here in GitHub.

Regards, Nikolay