I have been dealing with this particular issue for 4 days and it is really frustrating. I have a page that has a couple of form fields. When one of the input field loses focus, the keyboard slides down as expected but then a white background is displayed in place of where the keyboard appeared. I have attached an image to demonstrate the problem.
http://i.stack.imgur.com/ZHsBB.gif
I am testing on a HTC One M8 running Android 4.4 using Ionic 1.0.0 and the Ionic Keyboard plugin. I really need help with this issue.
Related
Hi im using a bootstrap modal and when opened the modal on an iphone and tap to write, the phone keyboard shows up and i noticed that a blank space at the bottom is added, anyone experienced this issue before, just happens on ios safari.
view issue here
Having the same issue since iOS update last week. Blank spaces in the code where my modals sit. The ‘fix’ is to clear history and website data in settings, but that is not great for customer experience. Hope we can find a solution
I have an input box that works fine on computers, but when browsing using ipad, the keyboard doesn't show up, so cannot type in anything. how would i bring up the keyboard upon entering the input box?
Update: I need to tap on the inputbox for a couple seconds, to bring the keyboard up. can there be more sensitive solution? I have ngTouch already and it's 1.3.0
I'm using sencha-touch 2.3.1 and cordova 3.4.0.
My app works well in android and ios devices. In windows, app works fine until I have a form in the page and when I select that form, the virtual keyboard is shown. After I'm done using the keyboard and close it, the whole app page seems to shift up a bit and it leaves a gap or horizontal bar at the bottom.
How can I fix this issue?
I'm implementing google maps api v3 in angularjs. I have two maps on the page: one shows the user's location and sits in the sidebar while the other allows users to add markers. This second map is only used in a form to add entries to the system.
It work fine in everything except mobile Safari on iOS 7. On an iPad running iOS 7 the side map works - ie: you can pan and zoom, but the other map is as if it's an image - no panning, zooming, or clicking to add a marker.
In the iPhone on iOS7 both maps are static, as if they're images. Debugging in Safari doesn't show any errors.
Debugging does show that they don't ever fire the click event to add markers.
The iPad on iOS6 is fine. Android is fine. Desktop browsers are fine.
I'm using Angular-ui ui.Maps to generate the maps.
I can't even think how to debug this further. Has anyone had trouble like this with iOS 7?
.
Is iOS7 mobile Safari the new IE? I've had quite a few issues now that only crop up on iOS7.
Update:
The Doctor was right. Here's the code to fix it:
$timeout(function(){
_.each(document.getElementsByClassName("gm-style"), function(e){
this.addEventListener('touchstart', function(event){});
});
}, 3000);
I get the sense that iOS7 Safari is a bit buggy when it comes to touch events.
I found this thread which talks about a specific touch event but I think other events have similar issues. `-webkit-overflow-scrolling: touch` broken for initially offscreen elements in iOS7
I searched for this and couldn't find any references to this.
In my iOS universal app, I wanted to display the information icon (same as the utility application) at the bottom right of my main view controller and use the same both for iPhone and iPad to flip over to display information about my app and other things. On the iPadd Utility application template with XCode 4.6, the information icon is displayed as a button on the navigation bar and a UIPopOver control is used to display information.
In my case, I don't want to use a UIPopOver on the iPad but use the same flip over effect both for iPhone and iPad when clicking the information icon. Is this a valid as per Apple's guidelines or guaranteed for rejection?.
I do exactly what you're thinking of doing in my app. I used the flip transition to display my info page using the information icon as the button image. I had no problems with Apple regarding this when I submitted.