Focus enter/exit properties not working in 1.4 [277234245]

Fixed

Bug

Status Update

No update yet.

Description

ra...@google.com

created issue #1

Apr 6, 2023 06:25PM

Launch the Demo app, and navigate to one of the following demos:

Framework > Focus > Explicit Enter/Exit Focus Group
Framework > Focus > LazyList Child Focusability

Notice that the enter/exit properties are not always triggered.

Comments

ra...@google.com <ra...@google.com> Apr 6, 2023 08:51PM

Accepted by ra...@google.com.

ap...@google.com <ap...@google.com> #2Apr 7, 2023 11:38PM

Marked as fixed.

May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.

pr...@google.com <pr...@google.com> #3Apr 19, 2023 06:12PM

Unfortunately I am unable to reproduce it as well. Maybe there is a chance you can share your code with me? You can send it to my email as you did previously already.
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?

co...@agilefreaks.com <co...@agilefreaks.com> #4Apr 28, 2023 10:24AM

It happens even on screens that does not use the layoutInfo it just require many up / down flings.

LazyColumn(state = rememberLazyListState())

The only thing all screen have in common in that they have multiple item {} item{} block :(

Just in case the app is in open beta at https://play.google.com/store/apps/details?id=app.symfonik.music.player but don't think you can see much except repro.

My main question before trying to do complex repro, is how much will it be relevant with all the recent changes in alpha 8 about Lazy stuff? And side question when https://issuetracker.google.com/issues/229752147 is fixed (it touches all my screens maybe another indicator?) will there be some snapshot build with the fix so I can directly try to repro on that?

na...@google.com <na...@google.com> #5May 3, 2023 06:24PM

I can't guarantee as I don't understand the issue yet, but I assume this issue is still not fixed, changes in alpha 8 were about different things. b/229752147 is fixed already in the main branch, so any recent snapshot from androidx.dev should contain it already if you want to try

Issue 277234245