Status Update
Comments
te...@gmail.com <te...@gmail.com> #3
Tested the issue on reported chrome version #87.0.4280.00 using Mac 10.13.6 as per the steps in https://crbug.com/chromium/1159587#c0
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
Description
<navigation xmlns:android="
xmlns:app="
android:id="@+id/main"
app:startDestination="@id/graph1">
<include app:graph="@navigation/graph1" />
<include app:graph="@navigation/graph2" />
<include app:graph="@navigation/graph3" />
<include app:graph="@navigation/auth" />
<action
android:id="@+id/action_to_auth"
app:destination="@id/auth"
app:popUpTo="@id/graph1"
app:popUpToInclusive="true"
app:launchSingleTop="true" />
<action
android:id="@+id/action_to_main"
app:destination="@id/graph1"
app:popUpTo="@id/auth"
app:popUpToInclusive="true"
app:launchSingleTop="true" />
</navigation>
I didn't want to make auth the start destination since i know that's not a best practice. I'm showing / hiding the bottom navigation bar depending if the user is on the auth flow or not.
When starting the app if the user is logged out i redirect to auth flow using the action_to_authand when he logs out, i’m calling navigate(R.id.action_to_auth) . The issue with multiple backstacks is that saved stacks aren’t cleared and there is no way to query what back stacks were previously saved into the fragment manager and have options on what do with them. Am i missing something and there is a better way to handling auth flow?