-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unfocus all the textfields in the app #137
Labels
easy
Easy level issue
enhancement
new feature requests
good first issue
good issue for first-time contributors
Hacktoberfest
For Hacktoberfest 2021
low-priority
Something that has a low priority
Comments
Mohitmadhav
added
easy
Easy level issue
enhancement
new feature requests
good first issue
good issue for first-time contributors
Hacktoberfest
For Hacktoberfest 2021
low-priority
Something that has a low priority
labels
Oct 8, 2021
Okay @keyurgit45, but your reply isn't showing here on Github |
Actually it is very easy issue so if any beginner wants to try he can try so I deleted my comment. We can focus on null safety |
Hey @Mohitmadhav ,I would like to work on this issue ,please assign it to me |
Cool @lalit-commits, just go through the README carefully |
8 tasks
Mohitmadhav
added a commit
that referenced
this issue
Oct 15, 2021
Fixes #137 Added dismissing keyboard feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
easy
Easy level issue
enhancement
new feature requests
good first issue
good issue for first-time contributors
Hacktoberfest
For Hacktoberfest 2021
low-priority
Something that has a low priority
Description
All the text fields should get dismissed when users type their entries. Check https://flutterigniter.com/dismiss-keyboard-form-lose-focus/. Look for all the text fields in the entire app which are not shown in this screenshot.
Screenshots
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Additional data
Add a screen recording of keyboard dismissal of any screen in your PR.
The text was updated successfully, but these errors were encountered: