UI5 mobile zooms in as soon as input field focus

[tobiasfue]

We have the problem that our mobile version of the UI5 app "zooms in" as soon as you touch/fcous an input field. Then you have to manually zoom out again. The layout looks good at first. Not too small, no overlaps etc.

Is there a way to prevent zooming in?

I found a <meta> header tag which is supposed to prevent this zoom, but how can I use a meta tag in a launchpad environment?

Thanks 🙂

[boghyon · Accepted solution]

This is a known issue in iOS/iPad devices. Should be already fixed with https://github.com/SAP/openui5/commit/96a1d29bf838cf39f0c98e39a13d2f78a5e75c90

1. Update to the latest available patch number of the maintained SAPUI5 version:

• Monthly release (currently 1.119)
• Or one of the long-term releases: 1.117, 1.114, and 1.108.

2. Ensure that `sap/ui/util/Mobile.init` is called. If the application uses one of the root controls below, it's called automatically:

• sap.m.App
• sap.m.SplitApp
• (sap.m.Shell for standalone apps)

3. The initial HTML document of the app frame might be served with its own `<meta name="viewport" content="..." />`. In that case, remove the meta tag to allow `sap/ui/util/Mobile.init` setting it for the app accordingly. If you cannot control setting the viewport meta tag in HTML, and the launchpad still sets its own viewport meta tag unexpectedly, create a customer case.

[tobias2022 · Accepted solution]

Hi Boghyon,

we are already at version 1.119 and I can see, that the root html frame has it own "viewport" tag. The viewport within the iframe looks good. How can I manipulate the html tags? Thanks!

[boghyon · Accepted solution]

tobias2022 Then you'd have to create a customer case since the app cannot control the outer frame of the launchpad. But I think FLP is already working on the issue.

[tobiasfue · Accepted solution]

Thanks, I will do that.

[boghyon · Accepted solution]

tobias2022 tobiasfue The statically added `<meta name="viewport" content="..." />` should be removed by now from the FLP's initial HTML on CF. If you can confirm that the issue is no longer reproducible based on my answer above, please consider closing this Q&A.