I have a login form with 2 text fields. When you focus on the email field, the password field gets hidden by the keyboard. The return key does bring you to the password field, and tapping outside of a text field dismisses the keyboard, so it's not completely unusable, but it's not very intuitive either.
It would be much better if both fields were kept in view, above the keyboard. With the old version of IQKeyboardManager where was the concept of IQLayoutGuideConstraint which was maybe useful here, but that whole thing is gone now.
Any tips? This is not a tableview nor a scrollview.
Related
I'm working on an App with Objective-C but I have a problem with my form.
I have several inputs view (UITextField) on it, and one with a particularly behavior.
When I select the checkbox, I prevent the user typing on the view and looks the view as disable( grayed out and without the blue bar flashing blue bar ) and keep the keyboard open.
When I set the UITextField as disable, the keyboard is automatically hidden.
Someone knows how to keep the keyboard open?
I need to something like the image attached, but without the blue bar flashing blue bar.
I did the logic to prevent the the user enter data on the input , but the keyboard is automatically hidden.
If the text field is disabled, the user cannot type into it and the dismissal of the keyboard is correct. You should not try to fight against that. (It sounds like you're trying to disable the keyboard for the wrong reasons anyway.)
In this case, it sounds like your timing is just off. When the user clicks the checkbox, your code responds. What you are doing there is just wrong. You should respond by moving the first responder to the next enabled text field yourself, and then disabling the first text field. That way, you are not disabling the text field while it is first responder; that's your whole mistake right there.
We are designing a custom keyboard on iOS with a TextField (Search Field) on it.
Problem - Not able to move the focus to and fro between our custom keyboard's search field and the third party app’s search field.
when the focus comes to the custom keyboard search field it never goes back to the Parent App's search field.
PS: I have seen the keyboard apps like Popkey and Fleksy successfully doing this.
I could find out a workaround to achieve required functionality by keeping a Label instead of textField. With this work around we don't have to worry about the focus issue. Once user starts typing, we need to catch the event and update the text in label.
Hope this will help if some one is still looking for a solution to this problem.
This might be kind of hard to explain in a way to easily understand.. but basically I am having an issue when first tapping into a text field. When the user starts typing text, if the text reaches the end of the textfield, rather than the view scroll with the cursor as the user continues to type, the cursor just stops at the end of the textfield, but the field continues to register inputs. if the user closes the keyboard, and re-enters the textfield then it actually works as it should, scrolling along with the new letters the user types beyond the length of the textfield.
Is this some strange setting I have on my text field? Is this a bug with iOS 8? I don't even know where to begin to look to solve this issue.
I have a long HTML form that I am trying to make accessible to Voiceover. When I click into a field, interact with it, and then click Done on the keyboard, after a short delay Voiceover is focusing on what appears to be the field most centered on the screen rather than the next element. I tried adding explicit tabindex to all the fields and this did not help. It is not always reproducable, it sometimes works as expected.
Is this expected behavior for Voiceover? Would a user not expect "Done" to take them to the next field (seems like maybe a dumb question since there is also a "Next" button, which works fine)? But as a sighted user I know the "Done" button when I am interacting with a field just means I am done with that field and want to go on to the next action, field whatever.
"Done" dismisses editing mode on VoiceOver. A VoiceOver user would not expect that tapping "done" moves the VO cursor.
I have 3 grids:- Header,Body and Footer with Body having textboxes.
I have included the Body inside a scrollviewer so that user can type as much data as he wants in the texboxes of Body.
But when the Keyboard pops up the whole view is pushed at top and I cannot see the Header.
The textboxes have wrapping on and also accepts return.
Can the scrollview move up the text when keyboard pops up?
Thanks and Regards,
Kanaya
Not entirely sure if this will help. How about some XAML?
You could capturing the Focus event of the text box that brings the Keyboard up. In that event you could set the scrollViewer.HorizontalOffset property to some caluclated value to get whatever you want in view.
Edit: HorizontalOffest is only a getter user ScrollToHorizontalOffset instead
You probably can make it scroll up like you want, but it will appear very strange to seasoned users of the WP7 operating system. Expected behavior for text input is exactly what you described, the notion Microsoft (I believe) is trying to hit here is that when you want to type something in, you want to clear everything else out of view, and only focus on the textbox at hand.