IssueTracker

BTW, the source code for this is fairly straightforward. I just added the source into the sample for now, but it would be nicer if we had the function.

From source:

 /**
 * Gets the current navigation back stack entry as a [MutableState]. When the given navController
 * changes the back stack due to a [NavController.navigate] or [NavController.popBackStack] this
 * will trigger a recompose and return the top entry on the back stack.
 *
 * @return a mutable state of the current back stack entry
 */
@Composable
public fun NavController.currentBackStackEntryAsState(): State<NavBackStackEntry?> {
    return currentBackStackEntryFlow.collectAsState(null)
}

Here's the code from my PR if you want to see what I was doing.

Hi Steve, which version of the library will this be released in?

Never mind, it's in alpha15, missed that. Thanks!

Note that if we change ListHeader to use Modifier.defaultMinSize(minHeight = 48.dp).height(IntrinsicSize.Min), then according to my testing, that allows developers to override the height in their own code, which is what the chat in comment 6 was originally about.

FWIW I notice that we have already made exactly this change in our Material3 codebase following a UX code review (see aosp/2715054)

@vincenttam Please will you confirm if we should make this change to expand the ListHeader to accommodate contents in Material 2.5 - thanks.

Yes, confirming from UX that we should update to ensure the ListHeader can accommodate contents for up to 3 lines of text (and behaviour is to push the content below further down as a result)

We made this update on SysUI for accessibility reasons, as Steve has noted in comment#6, to ensure scalability for larger text sizes and also localized strings