Here’s a sample app:
Clone link:
I have two forms in this app. The first one is just to capture some input in a text box, then the second form opens, and on the form_show event I have it set to “scroll_into_view” on the top-most button.
Try running this in Chrome on iOS, and Safari on iOS.
In Safari, the scroll_into_view works correctly, immediately displaying the entire button when the second form opens.
In Chrome, the button will not be displayed properly. And when you scroll down to the very bottom of the form, the other button will also be hidden (the second button at bottom also triggers a button_1.scroll_into_view() event on click). In fact, the entire scrollbar on the device seems to get out of whack on that page. Try playing around with it, scrolling to the very bottom, pressing the button, then getting teleported to the top, and trying to swipe up afterwards to display the whole button.
Is it some kind of bad JS implementation on Chrome? It seems like it might be related to the device’s keyboard popup that’s causing an incorrect sizing of the viewport in the browser afterwards? Thoughts?
EDIT: I just added another button to the opening form, allowing you to go to the 2nd form without typing anything. If you use this, Chrome opens the second form and displays the upper button properly, as expected. But if you type something in, the top button is not properly shown when the 2nd form opens. However both browsers exhibit some bizarre behaviour on the 2nd form, either hiding the bottom or top buttons from display unless you swipe several times to “force” the page down. And the scrollbars seem to double and look funny.