MotionEvents dispatched to Android inside of Compose must have accurate positions. [158034713]

Fixed

Bug

Status Update

No update yet.

Description

sh...@google.com

created issue #1

Jun 2, 2020 10:59PM

Currently, the MotionEvents that are dispatched to Android Views that are hosted in Compose do not have completely accurate raw and offset positions. This will be at least partially addressed by a fix for

b/157728190

but future other changes in interop (such a fix for

b/158016274

) will require more changes to make this so.

For future record keeping: as of very soon (after the fix for

b/157728190

lands), I believe the solution will be to update PointerInteropFilter's call to toMotionEventScope to not take the locationInWindow of the view as it will soon be doing, but instead to take the global location via PointerInteropFilter's position property.

Comments

sh...@google.com <sh...@google.com> #2Jun 4, 2020 07:11PM

Fix should be a release of androidx.activity 1.3.0-alpha02 from build ab/7134643

ap...@google.com <ap...@google.com> #3Jul 21, 2020 12:07AM

Marked as fixed.

Activity 1.3.0-alpha02 has been released and fixes this issue as well as fixing the issue:

Class 'androidx.activity.compose.ComponentActivityKt' is compiled by an unstable version of the Kotlin compiler and cannot be loaded by this compiler

Apps using Compose alpha12 and specifically artifacts like androidx.compose.ui:ui-test-junit4:1.0.0-alpha12 that internally use setContent should add the activity-compose:1.3.0-alpha02 dependency to their dependencies block to ensure that the 1.3.0-alpha01 artifact is not used:

implementation 'androidx.activity:activity-compose:1.3.0-alpha02'

Issue 158034713

Description

Issue summary

Comments

sh...@google.com <sh...@google.com> #2Jun 4, 2020 07:11PM

ap...@google.com <ap...@google.com> #3Jul 21, 2020 12:07AM

Add comment

Issue metadata