App distorted by auto zoom input select

[david2]

Seems like you guys pushed an update that defaults the device to auto zoom on input select. Can you please pull this change out of production unless there's a way to disable this feature at the control level?

[Anonymous]

This is terrible service by Microsoft. Obviously there is something that can be done for ComboBoxes.

They are correct to say that for textInputs with small fonts, ios will autozoom. For these, you can just increase the font size. However, for ComboBoxes, it doesn't matter what the font size is. I change it to massive fonts, it still zooms in every time it is selected.

Horrendous user experience. I can't believe this hasn't been fixed.

[testasdfasfsafa]

I have the same problem on iOS.

[Anonymous]

"To fix this issue, ensure that the font size of text inputs are large enough so that iOS does not have to zoom in."

Not true, combo box will always zoom in and stay there, so the bug is in PowerApps side... users needs to zoom out manually all the time. We cannot use PowerApps as a mobile app platform with this future enabled. This is not a minor but a major problem. Microsoft needs allow costumer to decide if their app needs this future or not. 

[NewcombR]

I agree. This is an issue. For Text Input, all I need to do is change the size of the font to 16 and the problem is solved. However, this doesn’t solve the issue for the Combo Box when the “Searchable” property is enabled. I suspect that this is because the “Search Text” text input on the Combo Box is smaller than the ComboBox’s Size property.

I don’t see any option to configure the ComboBox’s search text input property, either. Instead of using a combo box (1 control), I’m having to configure multiple controls to achieve the same functionality. eg Text Input + Gallery for searching.

I need to configure the Gallery’s Items property based on whether the Text Input text property, and also the Gallery’s visibility property to the show/hide based on whether the Text Input field contains data.

Then, I need to configure a Label control to display the selected item, or either a list box or another gallery to display the selected items (if the user needs to select more than 1).

Then, I need to setup logic to handle resets on all 3 controls.

Moreover, if this is a responsive app I need to setup the responsive properties for all the controls as well, including the controls internal to the gallery.

This is all to replace 1 ComboBox. Very inefficient. If there are multiple ComboBoxes, this becomes a real hassle. If components could utilize data sources, I could create a component to avoid having to rebuild these controls every time... however, that isn’t an option right now.

The only repeatable/reusable component could be an a component that utilizes a connector rather than a data source (e.g. Office365.SearchUsers).

However, if I wanted to build a reusable component for something like Contacts or Accounts in CDS, I can’t because data sources can’t be used.

[NewcombR]

I agree. This is an issue. For Text Input, all I need to do is change the size of the font to 16 and the problem is solved. However, this doesn’t solve the issue for the Combo Box when the “Searchable” property is enabled.  I suspect that this is because the “Search Text” text input on the Combo Box is smaller than the ComboBox’s Size property.  I don’t see any option to configure the ComboBox’s search text input property, either. Instead of using a combo box (1 control), I’m having to configure multiple controls to achieve the same functionality. eg Text Input + Gallery for searching. I need to configure the Gallery’s Items property based on whether the Text Input text property, and also the Gallery’s visibility property to the show/hide based on whether the Text Input field contains data. Then, I need to configure a Label control to display the selected item, or either a list box or another gallery to display the selected items (if the user needs to select more than 1). Then, I need to setup logic to handle resets on all 3 controls. Moreover, if this is a responsive app I need to setup the responsive properties for all the controls as well, including the controls internal to the gallery. This is all to replace 1 ComboBox.  Very inefficient.  If there are multiple ComboBoxes, this becomes a real hassle. If components could utilize data sources, I could create a component to avoid having to rebuild these controls every time... however, that isn’t an option right now.  The only repeatable/reusable component could be an a component that utilizes a connector rather than a data source (e.g. Office365.SearchUsers). However, if I wanted to build a reusable component for something like Contacts or Accounts in CDS, I can’t because data sources can’t be used.

[rolivier]

Any update on your request?  This is causing real issues for my users.  

[lmadsen]

I have the same problem, it is related to the font size on the iPhone. If I set text size low enough the app will zoom, as soon as I get above a certain text size I get the zooming behavios.

[LenC]

Was this solved anytime in the last three years?

I would point out that the new Modern Controls default to a font size of 10.5. This seems to be the direction for this next phase of UI standard. Unfortunately, this is bringing out the zoom issue on iPhone.