Async onValueChange for TextField with String value causes cursor to jump [160257648]

WAI

Bug

Status Update

No update yet.

Description

na...@gmail.com

created issue #1

Jul 1, 2020 02:30PM

When using, for example, an OutlinedTextField with the constructor that takes a String value, the caret will randomly (?) jump one index back from where it should be.

Steps to reproduce:
1. Use OutlinedTextField with the String-based constructor in any composable function
2. Type something long (a sentence or something) into the field
3. Observe the cursor randomly being placed before the letter that was just typed

This is easily worked around by using the constructor that takes a TextFieldValue as value, but should be fixed nonetheless.

Comments

na...@gmail.com <na...@gmail.com> #2Jul 1, 2020 02:31PM

    assertTrue(Double.NaN.coerceIn(0.0, 1.0).isNaN())
    assertTrue(Double.NaN.coerceIn(0.0..1.0).isNaN())

https://github.com/JetBrains/kotlin/blob/master/libraries/stdlib/test/ranges/CoercionTest.kt

si...@google.com <si...@google.com> Jul 10, 2020 07:02PM

Reassigned to si...@google.com.

si...@google.com <si...@google.com> Jul 28, 2020 05:51PM

Accepted by si...@google.com.

so...@google.com <so...@google.com> #3Aug 6, 2020 03:26PM

Low-hanging fruit. Shalom, mind taking a look during your work for PIs and loaders?

Message last modified on Aug 6, 2020 03:26PM

na...@gmail.com <na...@gmail.com> #4Aug 6, 2020 06:25PM

We can check for NaN, but what is the expected behavior here if a NaN is passed in?

We can throw an exception, but that would end in the same result you are experiencing now (i.e. a crash if you don't handle it)
We can just set the progress to zero in cases of NaNs, but then you would not be able to tell that you have a problem in your implementation and you are passing in illegal values.
We can document it that we only expect a non NaN values, but that seems a bit redundant and we don't usually adding these to the docs as it's implicit in most cases.

na...@gmail.com <na...@gmail.com> #5Aug 7, 2020 10:38AM

On my end, I discovered it was caused by division by zero and just set the bar to indeterminate in that case.

so...@google.com <so...@google.com> #6Aug 7, 2020 01:39PM

Status: Won't Fix (Not Reproducible)

I also experience this crash in our released app, I can reproduce this with both Material2 and Material3 with latest stable and alpha-versions, but only with enabled Talkback-service.

Since this crash only happens with enabled Talkback-service and the app works fine otherwise, I consider this to be a bug in the interaction between Talkback and the participating Material-compose frameworks.

build.gradle:

    implementation "androidx.compose.material:material:1.8.0-alpha08"
    implementation "androidx.compose.material3:material3:1.4.0-alpha06"

Minimal reproducible examples:

@Preview
@Composable
private fun MinimalReproducibleExampleM2Preview() {
    androidx.compose.material.LinearProgressIndicator(
        modifier =
            Modifier
                .fillMaxWidth()
                .height(12.dp),
        progress = 0f / 0f,
    )
}

@Preview
@Composable
private fun MinimalReproducibleExampleM3Preview() {
    androidx.compose.material3.LinearProgressIndicator(
        modifier =
            Modifier
                .fillMaxWidth()
                .height(12.dp),
        progress = { 0f / 0f },
    )
}

Crash in Material2:

FATAL EXCEPTION: main (Ask Gemini)
Process: de.billiger.android, PID: 416
java.lang.IllegalArgumentException: current must not be NaN
	at androidx.compose.ui.semantics.ProgressBarRangeInfo.<init>(SemanticsProperties.kt:662)
	at androidx.compose.foundation.ProgressSemanticsKt$progressSemantics$1.invoke(ProgressSemantics.kt:53)
	at androidx.compose.foundation.ProgressSemanticsKt$progressSemantics$1.invoke(ProgressSemantics.kt:51)
	at androidx.compose.ui.semantics.CoreSemanticsModifierNode.applySemantics(SemanticsModifier.kt:59)
	at androidx.compose.ui.node.LayoutNode$collapsedSemantics$1.invoke(LayoutNode.kt:442)
	at androidx.compose.ui.node.LayoutNode$collapsedSemantics$1.invoke(LayoutNode.kt:433)
	at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:2496)
	at androidx.compose.runtime.snapshots.SnapshotStateObserver$ObservedScopeMap.observe(SnapshotStateObserver.kt:460)
	at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:244)
	at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:133)
	at androidx.compose.ui.node.OwnerSnapshotObserver.observeSemanticsReads$ui_release(OwnerSnapshotObserver.kt:121)
	at androidx.compose.ui.node.LayoutNode.getCollapsedSemantics$ui_release(LayoutNode.kt:433)
	at androidx.compose.ui.semantics.SemanticsNodeKt.SemanticsNode(SemanticsNode.kt:49)
	at androidx.compose.ui.semantics.SemanticsNode.fillOneLayerOfSemanticsWrappers(SemanticsNode.kt:278)
	at androidx.compose.ui.semantics.SemanticsNode.unmergedChildren$ui_release(SemanticsNode.kt:257)
	at androidx.compose.ui.semantics.SemanticsNode.getChildren$ui_release(SemanticsNode.kt:338)
	at androidx.compose.ui.semantics.SemanticsNode.getChildren$ui_release$default(SemanticsNode.kt:322)
	at androidx.compose.ui.semantics.SemanticsNode.getReplacedChildren$ui_release(SemanticsNode.kt:305)
	at androidx.compose.ui.platform.SemanticsUtils_androidKt.getAllUncoveredSemanticsNodesToIntObjectMap$findAllSemanticNodesRecursive(SemanticsUtils.android.kt:195)
	at androidx.compose.ui.platform.SemanticsUtils_androidKt.getAllUncoveredSemanticsNodesToIntObjectMap(SemanticsUtils.android.kt:230)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.getCurrentSemanticsNodes(AndroidComposeViewAccessibilityDelegateCompat.android.kt:311)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.createEvent(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1577)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendEventForVirtualView(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1519)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendEventForVirtualView$default(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1509)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendSubtreeChangeAccessibilityEvents(AndroidComposeViewAccessibilityDelegateCompat.android.kt:2377)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.boundsUpdatesEventLoop$ui_release(AndroidComposeViewAccessibilityDelegateCompat.android.kt:2251)
	at androidx.compose.ui.platform.AndroidComposeView.boundsUpdatesAccessibilityEventLoop(AndroidComposeView.android.kt:1639)
	at androidx.compose.ui.platform.WrappedComposition$setContent$1$1$1$1.invokeSuspend(Wrapper.android.kt:148)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
	at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
	at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.doFrame(AndroidUiDispatcher.android.kt:68)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1299)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1309) (Ask Gemini)
	at android.view.Choreographer.doCallbacks(Choreographer.java:923)
	at android.view.Choreographer.doFrame(Choreographer.java:847)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1283)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8762)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@93d2fd8, androidx.compose.runtime.BroadcastFrameClock@cb15f31, StandaloneCoroutine{Cancelling}@36ca616, AndroidUiDispatcher@ae19b97]

Crash in Material3:

FATAL EXCEPTION: main (Ask Gemini)
Process: de.billiger.android, PID: 4219
java.lang.IllegalArgumentException: current must not be NaN
	at androidx.compose.ui.semantics.ProgressBarRangeInfo.<init>(SemanticsProperties.kt:662)
	at androidx.compose.ui.semantics.ProgressBarRangeInfo.<init>(SemanticsProperties.kt:655)
	at androidx.compose.material3.ProgressIndicatorKt$LinearProgressIndicator$3$1.invoke(ProgressIndicator.kt:156)
	at androidx.compose.material3.ProgressIndicatorKt$LinearProgressIndicator$3$1.invoke(ProgressIndicator.kt:155)
	at androidx.compose.ui.semantics.CoreSemanticsModifierNode.applySemantics(SemanticsModifier.kt:59)
	at androidx.compose.ui.node.LayoutNode$collapsedSemantics$1.invoke(LayoutNode.kt:442)
	at androidx.compose.ui.node.LayoutNode$collapsedSemantics$1.invoke(LayoutNode.kt:433)
	at androidx.compose.runtime.snapshots.Snapshot$Companion.observe(Snapshot.kt:2496)
	at androidx.compose.runtime.snapshots.SnapshotStateObserver$ObservedScopeMap.observe(SnapshotStateObserver.kt:460)
	at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:244)
	at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:133)
	at androidx.compose.ui.node.OwnerSnapshotObserver.observeSemanticsReads$ui_release(OwnerSnapshotObserver.kt:121)
	at androidx.compose.ui.node.LayoutNode.getCollapsedSemantics$ui_release(LayoutNode.kt:433)
	at androidx.compose.ui.semantics.SemanticsNodeKt.SemanticsNode(SemanticsNode.kt:49)
	at androidx.compose.ui.semantics.SemanticsNode.fillOneLayerOfSemanticsWrappers(SemanticsNode.kt:278)
	at androidx.compose.ui.semantics.SemanticsNode.unmergedChildren$ui_release(SemanticsNode.kt:257)
	at androidx.compose.ui.semantics.SemanticsNode.getChildren$ui_release(SemanticsNode.kt:338)
	at androidx.compose.ui.semantics.SemanticsNode.getChildren$ui_release$default(SemanticsNode.kt:322)
	at androidx.compose.ui.semantics.SemanticsNode.getReplacedChildren$ui_release(SemanticsNode.kt:305)
	at androidx.compose.ui.platform.SemanticsUtils_androidKt.getAllUncoveredSemanticsNodesToIntObjectMap$findAllSemanticNodesRecursive(SemanticsUtils.android.kt:195)
	at androidx.compose.ui.platform.SemanticsUtils_androidKt.getAllUncoveredSemanticsNodesToIntObjectMap(SemanticsUtils.android.kt:230)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.getCurrentSemanticsNodes(AndroidComposeViewAccessibilityDelegateCompat.android.kt:311)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.createEvent(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1577)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendEventForVirtualView(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1519)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendEventForVirtualView$default(AndroidComposeViewAccessibilityDelegateCompat.android.kt:1509)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.sendSubtreeChangeAccessibilityEvents(AndroidComposeViewAccessibilityDelegateCompat.android.kt:2377)
	at androidx.compose.ui.platform.AndroidComposeViewAccessibilityDelegateCompat.boundsUpdatesEventLoop$ui_release(AndroidComposeViewAccessibilityDelegateCompat.android.kt:2251)
	at androidx.compose.ui.platform.AndroidComposeView.boundsUpdatesAccessibilityEventLoop(AndroidComposeView.android.kt:1639)
	at androidx.compose.ui.platform.WrappedComposition$setContent$1$1$1$1.invokeSuspend(Wrapper.android.kt:148)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
	at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
	at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.doFrame(AndroidUiDispatcher.android.kt:68) (Ask Gemini)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1299)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1309)
	at android.view.Choreographer.doCallbacks(Choreographer.java:923)
	at android.view.Choreographer.doFrame(Choreographer.java:847)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1283)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8762)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@f9ecebb, androidx.compose.runtime.BroadcastFrameClock@93d2fd8, StandaloneCoroutine{Cancelling}@cb15f31, AndroidUiDispatcher@36ca616]

na...@gmail.com <na...@gmail.com> #7Aug 7, 2020 02:53PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Shalom Gibly <sgibly@google.com>
Link: https://android-review.googlesource.com/3461097

Prevent a crash when Float.NaN is a progress value

Expand for full commit details

Prevent a crash when Float.NaN is a progress value 
 
- Check for a NaN value and return zero if a progress lambda is 
  producing it and passing it into a `ProgressBarRangeInfo`. The range 
  info will throw an exception if a NaN is passed in. 
- Applied the check at the progress indicators (M3 & M2), and at the 
  loading indicator. 
- The remaining implementation does not cras on NaN, but the UI usually 
  does not render anything. 
- Also, switched to use `fastCoerceIn` instead of `coerceIn`. 
 
Test: Added 
Fixes: 352364576 
Relnote: "Fixed a crash at the progress and loading indicators in case a 
Float.NaN is passed in as a progress." 
 
Change-Id: I4fa969a1d46358a6f1db8b28cb0a375a809102c2

Files:

M compose/material/material/src/commonMain/kotlin/androidx/compose/material/ProgressIndicator.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/LoadingIndicatorTest.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/ProgressIndicatorTest.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/WavyProgressIndicatorTest.kt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/LoadingIndicator.kt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/ProgressIndicator.kt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/WavyProgressIndicator.kt

Hash: bf90726d0c7fadd916c5c8bf38b18f6a9a5d7a6b
Date: Wed Jan 22 16:28:41 2025

so...@google.com <so...@google.com> Aug 7, 2020 03:33PM

Status: Assigned (reopened)

si...@google.com <si...@google.com> #8Sep 30, 2020 11:35PM

Reassigned to an...@google.com.

Thank you!

an...@google.com <an...@google.com> #9Oct 1, 2020 01:57PM

Reassigned to si...@google.com.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.material3:material3:1.4.0-alpha08
androidx.compose.material3:material3-android:1.4.0-alpha08
androidx.compose.material3:material3-jvmstubs:1.4.0-alpha08
androidx.compose.material3:material3-linuxx64stubs:1.4.0-alpha08

device-2020-10-01-145354.mp4

1.1 MB

Download

si...@google.com <si...@google.com> #10Oct 2, 2020 02:14AM

Reassigned to ad...@google.com.

The delayed recompose does not fit to the current execution model of TF. TF expects the value to be set or not set; but not a delay. In the current case we can't handle delayed "resets" (since meanwhile user writes something and the new value is basically a reset).

Adam, Leland, I still need to read some documents but is this related to the current coroutine effort? If not do you have any opinions on how to solve the issue.

an...@google.com <an...@google.com> #11Oct 2, 2020 04:07PM

I am pretty sure it is not related to coroutines in any way. The issue here is that TextField pretends to be stateless and in fact it is not. The API makes you think you as a user is in control on how and when to change the text. If the component has `value`, `onValueChange` params in Compose it means it is stateless, and you as a user can ignore the value passed in onValueChange, or modify it, or apply it with some delay. And it will work for all other Compose components following similar pattern. But seems like it is not possible for TextField as it has internal state - the keyboard state. This means TextField can't use `value`, `onValueChange` params pattern and should be refactored pretty dramatically. And I think it is really important to do it before 1.0. We can't say developers to never apply values received from `onValueChange` with a delay as like it is not supported.

si...@google.com <si...@google.com> Oct 13, 2020 04:28PM

Reassigned to si...@google.com.

si...@google.com <si...@google.com> #12Nov 2, 2020 04:47PM

checked this. it is either not possible or not worth a change or trick with the current TextFieldValue API. We are planning to change that API and will consider this as a part of it.

si...@google.com <si...@google.com> Nov 13, 2020 04:50PM

Accepted by si...@google.com.

si...@google.com <si...@google.com> Nov 16, 2020 06:56AM

Assigned to si...@google.com.

na...@gmail.com <na...@gmail.com> #13Mar 15, 2021 01:23PM

Since there should be no major API changes anytime soon now, what's the status on this issue?

si...@google.com <si...@google.com> Oct 8, 2021 03:02PM

Reassigned to an...@google.com.

ji...@gmail.com <ji...@gmail.com> #14Jun 27, 2022 09:49AM

Whats the status of this ?

ma...@gmail.com <ma...@gmail.com> #15Aug 4, 2022 06:07AM

This still happens in Compose 1.3.0-alpha02, see duplicated issues for new steps and code (https://issuetracker.google.com/issues/240449669, https://issuetracker.google.com/issues/240455030)

This seems like a pretty big oversight as it makes validation of the text fields (such as preventing user from entering more than N characters) very bad experience for the user. And no responses since 2020...

Message last modified on Aug 4, 2022 06:13AM

ub...@gmail.com <ub...@gmail.com> #16Aug 26, 2022 11:10AM

This is easily worked around by using the constructor that takes a TextFieldValue as value, but should be fixed nonetheless.

I would be very interested in the reporter's "easy workaround" using the TextFieldValue constructor. How does that work? When I'm trying to use it, I'm only able to enter one char as a user and no more...

ub...@gmail.com <ub...@gmail.com> #17Aug 26, 2022 11:38AM

I hacked around the issue in the following way:

Before:

// asyncSource comes from the View Model and is changed via `changeText()`
OutlinedTextField(
    value = asyncSource.data,
    onValueChange = {
        viewModel.changeText(it)
    }
)

After:

// asyncSource comes from the View Model and is changed via `changeText()`
var inputText by remember(asyncSource.data) { mutableStateOf(asyncSource.data) }
OutlinedTextField(
    value = inputText,
    onValueChange = {
        inputText = it
        viewModel.changeText(it)
    }
)

I recognize that this is actually duplicating some of the logic, but I didn't have the jumping cursor issue anymore and still retain all flexibility of using asynchronous handling in my View Model and as a data source for the UI.

da...@facile.it <da...@facile.it> #18Feb 13, 2023 02:56PM

Hi, this is a 2020 bug which has undirectely been pointed out also in this -> https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5 article which actually cites the solution of the last user and is written by a Google spokeperson. It's a very spread one and impacts a LOT of developer and consequently a lot of user. It should be taken a little more seriously maybe. This fix is also not usable by kmm developers as pointed out inside a lot of comment of the above mentioned article and it's also very frustrating for people whose app has a lot or even more than 3 text fields.
Please, at least start to work on this issue.

si...@google.com <si...@google.com> #19Feb 13, 2023 04:57PM

Thanks for the comment.

The team already has started working on general structure of the TextField API since the current API and structure does not allow us to move forward with this ticket.

si...@google.com <si...@google.com> #20Mar 13, 2023 11:45PM

Accepted by kl...@google.com.

updated the assignee (one of Halil, Zach but can set only one), and also the priority to communicate that the work is ongoing in buganizer.

ro...@oda.com <ro...@oda.com> #21Mar 14, 2023 02:12PM

Hey, regarding this issue, i also notified that :
D/InsetsController: show(ime(), fromIme=true)
is called infinite times, when the mutableState is in the viewModel and i start writing in the textField.
On some devices it work, on others you are stuck after the first character.

Is this fix going to be in 1.4.0 final?

Message last modified on Mar 14, 2023 02:13PM

va...@gmail.com <va...@gmail.com> #22Mar 26, 2023 10:50AM

Hi. I stick to compose 1.2 in several apps with large amount of text fields because of this issue. Are there any plans to deal with it in 1.5? Or it might be "in progress" for more than one release-cycle?

ha...@google.com <ha...@google.com> #23Mar 26, 2023 11:25PM

Yes, the work on this bug and related issues regarding TextField state was started a while ago. 1.5-alpha01 release includes some of this work.

It's unlikely that anything will be finalized in one release-cycle but the upcoming changes will be initially released as Experimental. So, the iterative changes won't be confined to alpha releases.

se...@gmail.com <se...@gmail.com> #24Apr 30, 2023 03:25PM

The solution in post #18 seems to work for me. Hoping this will be fixed soon officially.

da...@decathlon.com <da...@decathlon.com> #25Jun 19, 2023 08:57AM

any news according this issue ?
thanks

st...@google.com <st...@google.com> #26Jun 19, 2023 09:04AM

Workarounds are outlined as per 18. The official solution is the new generation of TextField APIs which will be coming in future releases of Compose.

st...@gmail.com <st...@gmail.com> #27Jul 10, 2023 09:13AM

Link above is for googlers only. Please share workarounds.

kl...@google.com <kl...@google.com> #28Jul 12, 2023 07:12PM

Comment 18 referenced this article: https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5

kl...@google.com <kl...@google.com> #29Oct 3, 2023 10:18PM

Status: Won't Fix (Intended Behavior)

Closing this since async onValueChange updates are not supported and will continue to not be supported.

ma...@gmail.com <ma...@gmail.com> #30Oct 4, 2023 06:42AM

Is this documented anywhere?

kl...@google.com <kl...@google.com> #31Oct 4, 2023 08:00PM

Yes: https://developer.android.com/jetpack/compose/text/user-input#state-practices

Also kind of implied by the kdoc but could be more clear.

It's also been explained in more detail in a few talks:

ap...@google.com <ap...@google.com> #32Oct 4, 2023 09:24PM

Project: platform/frameworks/support
Branch: androidx-main

commit 125070eab17fd3d941e8718ec8a5b9b0d88ee3b4
Author: Zach Klippenstein <klippenstein@google.com>
Date: Wed Oct 04 13:14:11 2023

Kdoc polish for BasicTextField.

- Moved all sample links to the bottom. When rendering kdoc, Studio
doesn't render code samples inline, it places them all at the end. Any
text that comes after the first sample link is not rendered at all. So
any important documentation must come before the first sample link or
it will not be shown when users are viewing docs in Studio.
- Cleaned up wording of state management caveats. Our async requirements
weren't obvious, so I stated them explicitly and linked to our more
detailed guide.

Relnote: "Improved documentation on `BasicTextField` regarding
`onValueChange` requirements."
Test: n/a
Bug:

b/160257648

Change-Id: I90fc9dea845dafbf35fd439fe7813b2a752d9189

M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/text/BasicTextField.kt

https://android-review.googlesource.com/2773284

pr...@google.com <pr...@google.com> #33Oct 18, 2023 08:42PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.foundation:foundation:1.6.0-alpha08
androidx.compose.foundation:foundation-android:1.6.0-alpha08
androidx.compose.foundation:foundation-desktop:1.6.0-alpha08

Issue 160257648

Description

Issue summary

Comments

na...@gmail.com <na...@gmail.com> #2Jul 1, 2020 02:31PM

si...@google.com <si...@google.com> Jul 10, 2020 07:02PM

si...@google.com <si...@google.com> Jul 28, 2020 05:51PM

so...@google.com <so...@google.com> #3Aug 6, 2020 03:26PM

na...@gmail.com <na...@gmail.com> #4Aug 6, 2020 06:25PM

na...@gmail.com <na...@gmail.com> #5Aug 7, 2020 10:38AM

so...@google.com <so...@google.com> #6Aug 7, 2020 01:39PM

na...@gmail.com <na...@gmail.com> #7Aug 7, 2020 02:53PM

so...@google.com <so...@google.com> Aug 7, 2020 03:33PM

si...@google.com <si...@google.com> #8Sep 30, 2020 11:35PM

an...@google.com <an...@google.com> #9Oct 1, 2020 01:57PM

si...@google.com <si...@google.com> #10Oct 2, 2020 02:14AM

an...@google.com <an...@google.com> #11Oct 2, 2020 04:07PM

si...@google.com <si...@google.com> Oct 13, 2020 04:28PM

si...@google.com <si...@google.com> #12Nov 2, 2020 04:47PM

si...@google.com <si...@google.com> Nov 13, 2020 04:50PM

si...@google.com <si...@google.com> Nov 16, 2020 06:56AM

na...@gmail.com <na...@gmail.com> #13Mar 15, 2021 01:23PM

si...@google.com <si...@google.com> Oct 8, 2021 03:02PM

ji...@gmail.com <ji...@gmail.com> #14Jun 27, 2022 09:49AM

ma...@gmail.com <ma...@gmail.com> #15Aug 4, 2022 06:07AM

ub...@gmail.com <ub...@gmail.com> #16Aug 26, 2022 11:10AM

ub...@gmail.com <ub...@gmail.com> #17Aug 26, 2022 11:38AM

da...@facile.it <da...@facile.it> #18Feb 13, 2023 02:56PM

si...@google.com <si...@google.com> #19Feb 13, 2023 04:57PM

si...@google.com <si...@google.com> #20Mar 13, 2023 11:45PM

ro...@oda.com <ro...@oda.com> #21Mar 14, 2023 02:12PM

va...@gmail.com <va...@gmail.com> #22Mar 26, 2023 10:50AM

ha...@google.com <ha...@google.com> #23Mar 26, 2023 11:25PM

se...@gmail.com <se...@gmail.com> #24Apr 30, 2023 03:25PM

da...@decathlon.com <da...@decathlon.com> #25Jun 19, 2023 08:57AM

st...@google.com <st...@google.com> #26Jun 19, 2023 09:04AM

st...@gmail.com <st...@gmail.com> #27Jul 10, 2023 09:13AM

kl...@google.com <kl...@google.com> #28Jul 12, 2023 07:12PM

kl...@google.com <kl...@google.com> #29Oct 3, 2023 10:18PM

ma...@gmail.com <ma...@gmail.com> #30Oct 4, 2023 06:42AM

kl...@google.com <kl...@google.com> #31Oct 4, 2023 08:00PM

ap...@google.com <ap...@google.com> #32Oct 4, 2023 09:24PM

pr...@google.com <pr...@google.com> #33Oct 18, 2023 08:42PM

Add comment

Issue metadata