Status Update
No update yet.
Comments
no...@google.com
mo...@google.com
ap...@google.com
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.
ap...@google.com
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.
je...@google.com
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.
Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus().
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.
Description
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. (pointerInteropFiltergets 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.pointerorandroidx.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?