forEachGesture() can lose events [251260206]

Fixed

Bug

Status Update

No update yet.

Description

mo...@google.com

created issue #1

Oct 5, 2022 09:55PM

forEachGesture is an extension of PointerInputScope and has a lambda also on PointerInputScope. It repeats the lambda, which must call awaitPointerEventScope inside it to find gestures. On each loop, it must enter and exit AwaitPointerEventScope and each time it exits, there is a chance that events get lost between gestures.

We need a new method that loops wholly within AwaitPointerEventScope so that events aren't lost. forEachGesture can't be deprecated because there are use cases where suspend functions or a coroutineScope belongs within the lambda block. But most gesture detectors don't need that.

Comments

ap...@google.com <ap...@google.com> #2Oct 12, 2022 01:35AM

Marked as fixed.

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

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

na...@google.com <na...@google.com> #3Oct 24, 2022 01:37PM

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?

Issue 251260206

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Oct 12, 2022 01:35AM

na...@google.com <na...@google.com> #3Oct 24, 2022 01:37PM

Add comment

Issue metadata