I'm getting this box when trying to press on the textformfield, it's rarely to happened by it look like a bug and it sticks to the screen even if I navigate to a different screen until I restart the app it disappears, did anyone faced something like this ?
This comes due to long press over text field,
If you want to avoid this you have to pass enableInteractiveSelection: false which avoids copy and paste and other interaction from user
Related
while cooming back from any screen to homescreen my keyboard pop-ups automatically which makes user experience bad.
Can someone tell me how to deal with this bug.
you can run this code everywhere you change page:
FocusManager.instance.primaryFocus?.unfocus()
github issue
Remove what you set in textfield as autofocus true.
Messing around with flutter and I must be missing it in the documentation somewhere because I'm not sure what this object or property is.
I am trying to use a multiline textformfield, and so to handle focus I've used
onTap: (){FocusScope.of(context).requestFocus(new FocusNode());},
What I've noticed is that I need to doubletap to reenter the form field now.
When I do double tap, I get this odd label/hint -- How can I remove or prevent it from showing?
Hint/Label?
Any info is appreciated :)
Edit: The reason I needed to double tap was because multi-line form fields switch the Pixel2 GO button to the newline button and prevents the user from exiting the keyboard cleanly.
Fixed by adding textInputAction: TextInputAction.go to the textformfield
If you just want to have the TextFormField work normally, you don't have to write your own onTap function. The built-in one works perfectly fine :)
I am currently working on an Ionic 5 and I am facing 2 issues with the keyboard.
When I click on the ion-input and the keyboard appears:
The ion-content is pushed up so it is right above the keyboard, which cause everything to be crammed. I tried a bunch of solutions, but none of them properly worked, and most of them involve android:windowSoftInputMode="adjustNothing", which leaves the ion-content as it is, hence the ion-input is not visible and so the user can't see what they're typing and they also can't see the next button, so they must first close the keyboard in order to see what they wrote and be able to move on to the next step.
When the keyboard is about to dismiss, it leaves a white space in the space it was taking up. It's only for a split second but it is visible and makes the app feel like it's slow or lagging.
These 2 issues seem to be very common as I found questions about them since 2014, and I tried most solutions mentioned in the answers but nothing seems to work.
I seem to be having this issue in this app only, but I know that it is not an ionic 5 issue as people faced the same issue in older versions.
What the structure of the page looks like, I had to close all code blocks so that I could take one screenshot:
android:windowSoftInputMode is ised for native fields (EditText,etc..) so when you click on native xml it will take effect. All what you need to do is in your androidManefist.xml on line applicarion or activity, there is keyboardresize="adjustResize" which is the default, change it to adjustPan and content will not be pushed up , instead keyboard will go up as actionsheet from bottom without effecting the content.
I need to focus a text input into the Facebook login popup. I am using a virtual keyboard to simulate a physical one, but when I click a key, the text input lose focus and the letter is not written into the field.
How could I maintain the focus in the text input?
I'm not sure if creating your own virtual keyboard is a smart idea since all mobiles already have one in there, you just need to set useSoftKeyboard in Flex.
Also, you can always remove focusability to your components by setting focusEnabled and hasFocusableChildren to false.
I finally came to another solution... Using getElementsByTagName('theElementID'), I could get a reference to the textInputs in the browser, and I could modify its attributes...
For example,
emailStringObject =this.html.htmlLoader.window.document.getElementById('email');
emailStringObject.value="example#correo.com"
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?