[Object Page]: The 'Enter/Exit FullScreen' icon button is unnecessarily displayed in responsive mode

[VidhiNPatel]

Describe the bug

The 'Enter/Exit FullScreen' icon button is unnecessarily displayed in responsive mode for the Object Page Component

Isolated Example

No response

Reproduction steps

1. Go to the storybook for https://ui5.sap.com/#/entity/sap.uxap.ObjectPageLayout/sample/sap.uxap.sample.ObjectPageBeforeNavigate
2. Using Chrome dev tools, toggle the device toolbar -> check the page & associated dialogs at 320px viewport width
3. Refresh the page after switching to get the responsive width view
4. Observed that the 'Enter/Exit Full Screen' icon button is displayed in responsive mode, but it serves no functional purpose.

Expected Behaviour

Remove the 'Enter/Exit Full Screen' icon button from responsive mode since it serves no functional purpose.

Screenshots or Videos

UI5 Web Components for React Version

2.12.0

UI5 Web Components Version

2.12

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 @VidhiNPatel

this is not related to ui5-webcomponents-react, but SAP/OpenUI5 related. Please raise the issue in the appropriate channel.

• OpenUI5: Create a GitHub issue in their repo
• SAPUI5: Create an incident in BCP

[Lukas742]

@VidhiNPatel I’ve realized that the screenshot comes from our Storybook. I was confused as you linked the SAPUI5 documentation. The buttons are defined on the app side and are only examples, so we’ll treat this as a documentation issue.

[VidhiNPatel]

Hi @Lukas742 ,

I didn't understand your answer. Could you please explain what you mean by "it's only for examples"? Also, why is this considered a documentation issue? We do not want the 'Enter/Exit Fullscreen' button to appear on the mobile screen. I noticed the same behavior in Storybook, which is why I created it as a defect.

[Lukas742]

@VidhiNPatel the buttons rendered there are optional and fully controllable, if you don't pass a button there, there won't be one rendered. It's only a documentation issue and not a bug, as it doesn't affect apps the component is used in - we only pass a button (in our documentation) that might not be necessary.