Children with offset don't handle pointerInput outside of the parent [192479655]

Fixed

Bug

Status Update

No update yet.

Description

as...@gmail.com

created issue #1

Jul 1, 2021 01:41PM

Jetpack Compose release version: 1.0.0-beta09 Android Studio Build: Bumblebee 2021.1.1 Canary 2

I have pointerInput modifier on Box and it's children:

Box(
    modifier = Modifier
        ...
        .pointerInput(...)
        ...
) {
    content()
    Box(
        modifier = Modifier
            .align(Alignment.BottomEnd)
            .offset(...)
            .pointerInput(...),
        ...
    )
    ...
}

The parent pointerInput works fine but the children pointerInput only detects events inside the parent (ignores the offset). If I remove the parent pointerInput, everything works fine.

I've attached a video and sample project. In the video, the drag only works when dragged from the red part that's overlapping the blue part.

Record_2021-07-01-19-02-17_0fd7c2ba4cec95d59d89d84648f8f503.mp4

753 KB

Download

PointerInputBug.zip

108 KB

Download

Comments

so...@google.com <so...@google.com> Jul 1, 2021 01:56PM

Assigned to mo...@google.com.

mo...@google.com <mo...@google.com> #2Aug 19, 2021 03:25PM

First of all thanks for this detailed issue.

This issue had been investigated thoroughly when it was first reported internally. The surprising detail in this report is that the issue is not reproducible before 1.7. I will look into this.

The main problem with POBox is the fact that it is deprecated. Since 2021 Sony has been shipping new Xperia devices with Gboard pre-installed. Although we are aware that there is still a considerable amount of users still using POBox, the described behavior is caused by POBox's noncompliant behavior with InputConnection and InputMethodManager documentation. However, this is understandable since TextView implementation was also not respecting the behavior that is expected from Editors.

Ultimately we have decided to enforce the documented behavior with specifically regards to when editors should call InputMethodManager.updateSelection. Also, although unconfirmed, there were traces of possible custom code being included in Sony OEM images that changed how InputMethodManager was notified from TextView. If POBox also depended on something like this, it would be impossible for Compose code to replicate the same unknown behavior.

mo...@google.com <mo...@google.com> #3Aug 30, 2021 08:59PM

Accepted by mo...@google.com.

If the investigation takes time, would it be possible to revert the surrounding implementation to 1.6.x equivalent?

Or is that option not available?

Even if the root cause is POBox, from the perspective of the app's customers, it looks like an app bug, so this issue is a blocker against updating Jetpack Compose.

ap...@google.com <ap...@google.com> #4Sep 3, 2021 10:28PM

Marked as fixed.

Just to be sure, it is dangerous to replace Compose TextField with Android View EditText as a workaround for this issue.

Compose 1.7 has a bug that causes ANR when the focus is on EditText. https://issuetracker.google.com/issues/369354336

Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus(). https://issuetracker.google.com/issues/374031296

Perhaps there is a lack of testing of Compose 1.7 in combination with Android View. There is also a possibility that there are other fatal bugs related to View.

In other words, the only options for apps targeting the Japanese market that require POBox support are to continue using Compose 1.6 or to use EditText in combination with various workarounds.

Issue 192479655

Description

Issue summary

Comments

so...@google.com <so...@google.com> Jul 1, 2021 01:56PM

mo...@google.com <mo...@google.com> #2Aug 19, 2021 03:25PM

mo...@google.com <mo...@google.com> #3Aug 30, 2021 08:59PM

ap...@google.com <ap...@google.com> #4Sep 3, 2021 10:28PM

Add comment

Issue metadata