sap.uxap.ObjectPageLayout - upperCaseAnchorBar does not work anymore after 1.108+

[fabiopagoti]

What is the issue and how can we reproduce it?

1. Open the sample Object Page with Title on top from class sap.uxap.ObjectPageLayout using different UI5 versions

Latest - Object Page with Title on top

1.108.50 - Object Page with Title on top

1.96.45 - Object Page with Title on top

2. Open file view/ObjectPageOnJSON.view.xml (should be the default file)
3. Identify the ObjectPageLayout (around row 10)
4. Change property upperCaseAnchorBar from false to true. For version 1.96, as it's not possible to change the source code from the sample, use the UI5 Diagnostics Dialog to manipulate this property

5. Check the section/tab names. They should all be in upper case
6. Actual results

• Version 1.96 -> Tiles are displayed in upper case
• Version 1.108, 1.120, 1.136, etc -> Titles are not displayed in upper case and then this property is ignored

Version range from 1.97 up to 1.107 were not checked as they are not supported anymore.

Expected behavior:

They should all be in upper case in all versions. The same issue happens if you manipulate property titleUppercase from classes sap.uxap.ObjectPageSection or sap.uxap.ObjectPageSubSection

Which OpenUI5 version is your project targeting?

1.136.14

Is the issue device- or browser-specific?

Tested in Edge Version 144.0.3719.115 (Official build) (64-bit)
Desktop

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[codeworrior]

As far as I can see, this is specific for the sap_horizon theme family. Looking into the design specs, the paragraph about Anchor Bar Navigation contains the following hint for developers:

Make sure that the UpperCaseAnchorBar property is disabled and that you enter the anchor bar labels in title case (for example: Contact Information).

I guess, the control enforces this part of the guideline in sap_horizon by explicitly disabling the upper case text transformation.

But control owners should comment on this.

[fabiopagoti]

Thanks @codeworrior for the great analysis. I'd never imagined this would be related with the theme and it makes sense are we are going from 1.71 to 1.136 due to a S/4HANA migration.

Still, I agree the control owners should have a feedback. It's weird to have such a different output depending on the theme when there is a property meant for that.

[50gY]

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