IssueTracker

Description:

TextFields that use the TextFieldState API within a composable passed to the detailPane parameter of a ListDetailPaneScaffold are not updated when selecting different items in the listPane.

The issue occurs after opening a ListDetailPaneScaffold and selecting an item for the first time: until then everything behaves as expected. However, when selecting a different item from the list, the content of the TextFields that use the TextFieldState API does not update and remains with the data of the at first selected item.

How to Reproduce:

0. Versions: group = "androidx.compose.material3.adaptive", name = "adaptive-navigation", version = "1.0.0"
1. Follow the example for ListDetailPaneScaffold as described in the official Jetpack Compose documentation:
   • Documentation: List-Detail Layouts in Compose
   • Example Code: GitHub Snippet
2. Modify the MyDetails(item: MyItem) implementation as follows:
   • Replace this code:

Text( text = "Details page for $text", fontSize = 24.sp, )

with

TextField( state = rememberTextFieldState("Details page for $text"), // fontSize = 24.sp, )

3. Click on different list items. The data of the first clicked item remains displayed and is not updated when a new item is selected.

Why I Reported This:

I initially interpreted the detailPane implementation in the example code

detailPane = { AnimatedPane { 
    // Show the detail pane content if selected item is available
   navigator.currentDestination?.content?.let { MyDetails(it) } } },

like this: I assumed that every time a list item is clicked, MyDetails would be recreated with the corresponding MyItem object as a parameter, and that this would trigger a recomposition and update the content of the TextField.

In Case This Behavior Is Intended:

If this behavior is intentional, I strongly recommend adding a note about how TextFields behave within a ListDetailPaneScaffold to the documentation. This behavior, while it might be logically based on Compose's internal principles, can be very confusing. I could not find any mention of this behavior or any guidance in the design guidelines regarding the use of TextFields within a ListDetailPaneScaffold.