Bug P2
Status Update
Comments
rv...@google.com <rv...@google.com> #2
Please include a sample project that reproduces your issue.
hu...@gmail.com <hu...@gmail.com> #3
Here is the sample project.
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
se...@philo.com <se...@philo.com> #4
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: `main`
Devices/Android versions reproduced on: Any TV running API version less than 32.
To reproduce:
1. Create a focusable node
2. Add a `BackHandler` that is enabled
3. Click back while the node has focus and observe that the back handler does not get invoked.
On API versions less than 32, the view is getting a crack at the back key event before the activity, and `AndroidComposeView` treats the event as a Focus Exit, thus swallowing the event. Therefore, the `BackHandler` never gets run.
See:
I don't think `Back` should be considered as a key event for `FocusSearch`.