IssueTracker

Doc changes when unhiding the API:

• WebMessageListener does not support ARRAY_BUFFER, review docs to make sure it clearly documented.
• WebMessageCompat: document getData and getArrayBuffer will return null, unless getType is equal to string or array buffer.
• WebMessagePortCompat: review docs and make sure new type is updated.

The following release(s) address this bug:

• androidx.webkit:webkit:1.6.0-alpha02

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

• androidx.webkit:webkit:1.8.0-alpha01

Re comment#6 - can you explain what you are talking about? A fragment based navigation system is not going to be using Navigation Compose, which is what this issue is about and which is already available via Accompanist Navigation Material to unblock any migration to Navigation Compose from a fragment based system.

BottomSheetDialogFragment, which is what you'd use in a fragment based system, has been supported since dialog destinations were added in Navigation 2.1.0-alpha03 back in 2019.

This has been added internally and will be released as part of the compose.material library, not navigation.

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

• androidx.compose.material:material:1.7.0-alpha04
• androidx.compose.material:material-android:1.7.0-alpha04
• androidx.compose.material:material-desktop:1.7.0-alpha04

I guess the release that addresses this is actually: androidx.compose.material:material-navigation:1.7.0-alpha04

As #13 said, we are missing this for Material3 bottom sheets. I see that there's another issue tracking that here: https://issuetracker.google.com/issues/328949006

Some guidance about usage would be very welcome. I get java.lang.IllegalStateException: Could not find Navigator with name "bottomSheet". You must call NavController.addNavigator() for each navigation type. crash and can't find any proper example of this new extension usage:

                Scaffold(
                    bottomBar = {...}
                      
                ) { innerPadding ->

                    NavHost(
                        navController,
                        startDestination = "explore_graph",
                        Modifier.fillMaxSize()
                    ) {
                        // nested graphs

                        bottomSheet("profile_bottom_sheet") { // CRASHES
                            Text("Bottom Sheet", Modifier.padding(16.dp))
                        }
                    }
                }
            }
        }
    }
}

I use androidx.compose.material:material-navigation:1.7.0-beta01, but my project is material3, could it be the reason?

Re comment#15 - Material Navigation works similarly to Accompanist, whose docs explain how to use it, including these two lines:

val bottomSheetNavigator = rememberBottomSheetNavigator()
val navController = rememberNavController(bottomSheetNavigator)

If you don't use those lines, you'd get that error message.