Status Update
No update yet.
Comments
on...@jacon.cz
Fundamentally the issue here is that the selection logic happening in composition depends on the text layout result which is available on measure. So we end up using stale TextLayoutResult which causes the issue.
al...@gmail.com
This is the same exception as in
rv...@google.com
There is a similar problem regarding Magnifier but I don't think these are directly related. The main cause for this issue is the async relation between TextFieldValue and layoutResult. Magnifier related crashes don't seem to be caused by changes in TextFieldValue or layout.
rv...@google.com
ap...@google.com
Branch: androidx-main
commit c1e913cdea06ac6cf01c596000d375013f1a1d7c
Author: Halil Ozercan <halilibo@google.com>
Date: Thu Jun 23 13:51:14 2022
Fix crash when selected text is cleared by state changes and re-added later
BasicTextField's String API manages the selection and composition completely internally. Therefore, its selection value stays the same across value changes that comes from hoisted state, instead of IME commands. In a case where selected text is removed by a state change and later added, text layout result lags behind. This change makes sure that selection handles are only drawn when layout result is in sync with the latest TextFieldValue.
Fix:
Fix:
Test: CoreTextFieldSelectionContentChangeTest.kt
Relnote: Fixed a crash where TextField is cleared and refilled while selection is active.
Change-Id: I1235b669921e67dcbec9e55a6d1a95ff609fe4b6
A compose/foundation/foundation/src/androidAndroidTest/kotlin/androidx/compose/foundation/text/CoreTextFieldSelectionContentChangeTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/text/CoreTextField.kt
vr...@gmail.com
Which version will this change be part of?
al...@gmail.com
vi...@google.com
FocusGroup was a stop-gap, which is no longer preferred. FocusRestorer is part of compose-foundation 1.6.0-alpha*.
You can find examples of how to use FocusRestorer in
Backhandler should work with FocusRestorer.
Also, please refer to this
[Deleted User] <[Deleted User]>
I continue to have problems with moving focus to first element in an unexplored row if I scroll the list. For example: I have a TvLazyColumn and it contains a list of TvLazyRow. For the first Rows all is ok, the focus goes on the first element and if I move up and down the focus is restored. But, if I scroll the entire list, for one of the new rows the focus is moved to another position like the position of an older row. It rememeber the focus.
Row 1 focus ok Row 2 focus ok Row 3 focus ok .... Row 10 it get focus of row 1 Row 11 gets focus of row 2 and so on
Description
Version used: 1.0.0-alpha05
When set some TvLazyRow into TvLazyColumn, the below problem is occurred
Item is focused according to changing direction by D-PAD. When changes from a current row to another, leanback keeps state current row item and starts from first index in new row list, but in compose android framework finds nearest focusable item and this item is focused