Disable scrolling on Soft Keyboard launch - iphone

I've been struggling with this for several days. I have a very simple page in my mobile app with a textarea input and when I click on it the soft keyboard appears and scrolls the header of my page out of view. Is there a way to prevent this default scrolling?

Your is the default functionality of Phones, When user completes typing the screen automatically scroll backs, Kindly check it, If it works please reply.

Related

In SAPUI5 can I disable fullscreen mode for sap.m.Input suggestions on mobile?

Is there a way to prevent a sap.m.Input with showSuggestion set to true from going into fullscreen mode when a mobile user focuses on it and enters text in it?
Here's a screenshot of what I'm talking about:
For my use case, 95% of the time users won't see a suggestion so having it enter fullscreen mode is very disruptive and confusing.
https://experience.sap.com/fiori-design-web/input-field/
Size S (Smartphones)
Cozy mode:
When the user clicks or taps the input field, a new full screen dialog opens in which suggested items can be selected. Here, the pop-in feature of the responsive table is used.
No, that's how the input control works on mobile.

White background shows when keyboard closes on Android

I am testing my app on HTC One M8 running Android version 5.0.2. When an input field in the app loses focus, a white background is shown after the keyboard closes.
My background image is set on .scroll-content, so I don't understand why it acts like this on Android.
Check your ionic pane colour and view colour. You have different background colour so in the keyboard adjust pane mode the view gets resized (height-keyboard height) so when the keyboard goes off it shows the ionic-pane colour. So override the '.pane' background colour and see will it make any difference.
keyboard adjustment will work only if '.scroll-content' is present. By default ionic-content will enable this
The issue is that when we open a keyboard in our current application the app gets resized to the area that is left after opening the keyboard and the Cordova webview is too slow in resizing the app back to its normal size after the user closes the keyboard. There is no proper solution to this problem.
The most elegant working workaround for is to stop resizing the application on keyboard open. The keyboard will just slide up and down on the form as an overlay and there will be no resizing required.
In AndroidManifest.xml file try to set windowSoftInputMode attribute to adjustNothing:
android:windowSoftInputMode="adjustPan"
This is not a solution and can be considered as an option for small forms but it is not suitable for big forms.

Customize/change keyboard buttons in iOS7, while using PhoneGap/Steroids

I'm part of a team building a mobile web app using AppGyver Steroids (PhoneGap). We are having an issue with the iOS7 keyboard displaying a very faint "Done" button on the keyboard when the user is operating in a text area or an input select. I suspect this is a problem that is actually global in our app, but these are the instances where I have observed them.
I've searched and searched for a solution or how to "customize" the keyboard in order to make this "Done" button more obvious, but I haven't found any solutions yet. Can anyone point me in the direction of how to adjust the "Done" button or any other keyboard/input controls?
Attached are two screenshots showing the issue.
http://i.stack.imgur.com/KeFYM.png
http://i.stack.imgur.com/h11IH.png
Have you seen the issue on github? It's now fixed. They'll be including the option for custom colours in the near future.

select menu inside a div with fixed position on mobile safari, iphone

I am building a site that has a header with a fixed position which contains a select menu. The header is supposed to stay locked to the top of the screen due to the position:fixed in css. However, when clicking the select menu in mobile safari on iphone, the header no longer stays locked to the top when the ios select menu opens. It seems that ios is centering the div with the select menu onto the visible area of the screen above the menu. This doesn't happen when the page is scrolled to the top, but when the address bar is not visible, it "breaks" like so. Haven't found any other answers, maybe I'm asking the question the wrong way. I can't post links to code yet, any help is appreciated.
http://selfconstruc.tv/menu-open.PNG
http://selfconstruc.tv/menu-closed.PNG
For now I don't think there is a perfect solution to deal with the focus jumping.
In my case I hide the header on focus in and show again in focus out and it works well.
I don't know if in your case this could be a workaround.
You can try this:
// detect ios device
if(navigator.userAgent.match(/(iPad|iPhone|iPod)/gi)){
// hide header on focus in and show on focus out
jQuery("#content").focusin(function(){
jQuery('#your-header-id').hide();
})
jQuery("#content").focusout(function(){
jQuery('your-header-id').show();
})
}
The #content is a div where you should have all your controls, the jQuery .focusin() detects the focus event on parent elements, so every control will trigger the focus event. You hide the header on focus and show after that. Hope this helps!

What event activates the keyboard in mobile safari

So the focus event causes the soft keyboard to come up for input fields. Im trying to find a way to stop this occuring. The reason is, as some of you may know, a click event has a 300ms delay before anything happens.
To get around this, we have implemented Googles FastButton http://code.google.com/mobile/articles/fast_buttons.html its working good after a minor tweak to also prevent a second mousedown, but if we click on a button and go to a second page that also has a input textfield, the keyboard still pops up.
I've tried preventing the touchend, mousedown, mouseend, click, firing again, and that helps it by not having the flashing cursor on the textfield but the keyboard is still there. If i blur the field you still see the keyboard popping up then disapparing which is not acceptable.
Any ideas?
Hmm... have you considered disabling the fields with disabled="disabled" while loading, and only then enabling them? It might let you get around the initial focused state that launches the keyboard, so that you can blur first, then enable?