Focus in route A is not restored upon going to route B and returning back to A [272302679]

Fixed

Bug

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

Mar 9, 2023 02:21PM

When we go from one route (A) to another (B) and then
Steps to reduce:
- Go from one route to another, while having an element focused
- Go back to the initial route
Actual behaviour - the focus is lost
Expected behaviour - the focus should be present

TvLazyRow was used as a demonstration, but the same bug is reproduced while using other components.

NB: The expected behaviour is present in components of Leanback library.

Additional notes on behaviour - If you use a sample project I attach you can observe, that position in the list is retained correctly, but the focus is lost. When you try to press LEFT/RIGHT button, the focus will be moved to a wrong item.
Example: Select element 2, press Enter, go back, press left -> the element 4 is selected.
Example: Select element 2, press Enter, go back, press right -> the element 1 is selected
Example: Select element 2, press Enter, go back, press Enter -> the element 1 is selected and navigation is triggered.

The issue is not device/android version specific.

While it is possible to implement saving/restoring focus on your own, it would be nice to have this this as an out the box feature, since custom solution complexity can significantly increase with complexity of a screen

deleted

Restricted

0 B

deleted

Restricted

0 B

Comments

ra...@google.com <ra...@google.com> Mar 10, 2023 06:13AM

Assigned to vi...@google.com.

my...@globallogic.com <my...@globallogic.com> #2May 18, 2023 02:22PM

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

Message last modified on May 18, 2023 02:23PM

vi...@google.com <vi...@google.com> #3May 18, 2023 02:25PM

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

ap...@google.com <ap...@google.com> #4Jun 2, 2023 11:25PM

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

ma...@gmail.com <ma...@gmail.com> #5Dec 7, 2024 05:41PM

deleted

rv...@google.com <rv...@google.com> #6Jan 6, 2025 08:44AM

Marked as fixed.

Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.

Issue 272302679