To properly handle dismissing bottom sheet dialog fragments, it's necessary to cancel the dialog instance instead of popping the backstack to receive all the desired Fragment callbacks. Previously, calling navigateBack() or navigateUp() would dismiss the bottom sheet, but leave the underlying WebView screen stuck on a screenshot instead of the interactive attached WebView.
To properly handle dismissing bottom sheet dialog fragments, it's necessary to cancel the
dialoginstance instead of popping the backstack to receive all the desiredFragmentcallbacks. Previously, callingnavigateBack()ornavigateUp()would dismiss the bottom sheet, but leave the underlyingWebViewscreen stuck on a screenshot instead of the interactive attachedWebView.Fixes https://github.com/hotwired/turbo-android/issues/197