Pointers/PointerEvents don't report pressure [205164819]

Verified

Feature Request

compose-roadmap-proposal

Status Update

No update yet.

Description

jt...@gmail.com

created issue #1

Nov 4, 2021 11:37PM

Description:

Android MotionEvents reports the pressure being applied to the screen by a finger, stylus or other pointer device.

There appears to be no way to get touch pressure in Jetpack Compose without resorting to pointerInteropFilter, which the documentation recommends we don't use and which in any case appears to break when inside a LazyItem scope. (pointerInteropFilter gets very janky, and drops around 90 per cent of events when in something like a LazyColumn.)

It would be nice if androidx.compose.ui.input.pointer or androidx.compose.ui.input.pointer.pointerevent (or indeed anywhere you liked!) contained pressure properties or methods.

Use Case:

Any Jetpack Compose drawing or handwriting app could make use of touch pressure. I imagine games could also benefit from it?

Comments

no...@google.com <no...@google.com> Nov 5, 2021 11:11PM

Assigned to mo...@google.com.

mo...@google.com <mo...@google.com> Apr 5, 2022 04:54PM

Reassigned to je...@google.com.

ap...@google.com <ap...@google.com> #2Jun 28, 2022 03:58PM

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

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

ap...@google.com <ap...@google.com> #3Jul 12, 2022 07: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?

je...@google.com <je...@google.com> #4Jul 12, 2022 07:38PM

Verified by je...@google.com.

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.

Issue 205164819