DynamicPage: Inconsistent Tooltip Text Across Pages ("Collapse Header" vs "Snap Header"

[samanr]

Describe the bug

here is an inconsistency in the tooltip text shown for the upward-facing arrow "collapse" button in the application. For the same icon that performs the same action (collapsing the header), the tooltip text is different depending on the page:

On the object page, the tooltip says "Collapse Header".
On the dynamic page, the tooltip says "Snap Header".

Both buttons are intended to perform the same action (collapsing the header), so the tooltip should be identical to maintain UX consistency.

Isolated Example

No response

Reproduction steps

1. Go to the Object page in the application.
2. Locate the upward-facing arrow button (collapse header icon) at the top of the page.
3. Hover over the button and observe the tooltip text (should display "Collapse Header").
4. Go to the Dynamic page in the application.
5. Locate the same upward-facing arrow button (collapse header icon) at the top of this page.
6. Hover over the button and observe the tooltip text (should display "Snap Header").
7. Compare the tooltip texts; notice they are different for the same icon and action.

Expected Behaviour

The tooltip should be Collapse Header for consistency.

Screenshots or Videos

UI5 Web Components for React Version

2.15.3

UI5 Web Components Version

2.15.0

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[Lukas742]

Hi @samanr

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues to clarify which tooltip is expected there.

---

Hi Colleagues,

I didn't find specifications for this, but when checking the sap.f.DynamicPage or the sap.uxap.ObjectPageLayout the tooltip is "Collapse Header" for both components, so I guess for consistency this should probably be adjusted in the DynamicPage. In case "Snap Header" is expected there, please let me know. We'll then adjust it in our ObjectPage implementation.