-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Selecting items from a list causes the keyboard to popup on Android. Also blocks back action. #4236
Comments
Ah, so this is as a result of being focusable I guess. I don't think the inoperable back button relates to this issue though. Are you sure you compiled using the latest |
Hello Andy, yes I'm using the latest fyne cli tool. $ fyne version
fyne cli version: v2.4.0 The interceptable back operation works fine, it's just that when the list is in focus and the keyboard pops, back stops working when sending multiple back actions. You can still make it work by tapping somewhere else inside the app as long as you're not tapping that same list widget. For my case I just disabled the list focus, so problem solved, but I do find this a bit annoying for the people who actually want their lists to be focusable. |
The focus issue is fixed. It would be good to know if your back button problem is still an issue after the list focus fix is applied... |
Sorry it appears the PR never got opened for some reason. up now. |
Fixed on develop, will merge it back into next release |
Checklist
Describe the bug
When I select the items from a list, this causes the keyboard to popup. Is there a scenario where we would require this? I tested it by compiling the list example here https://developer.fyne.io/collection/list
As a side effect, after you select an item, doing the back action multiple times in an attempt to exit the app, stops working.
How to reproduce
Screenshots
No response
Example code
Fyne version
v2.5.0
Go compiler version
1.21.0
Operating system and version
Android 10
Additional Information
No response
The text was updated successfully, but these errors were encountered: