You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
I'm migrating my app using the new component routing approach. I came across the following issue : if I specify the useAsDefault attribute in a route, the rule is correctly applied and I get directed to the expected component. But, if I click on the browser's Back button, it stays on the same page. Looks like it goes back to the previously requested page then the route rule is applied again etc...
I think that the state should be saved in the history with replaceState instead of pushState in case of 'useAsDefault' redirection...
The text was updated successfully, but these errors were encountered:
Hi,
I'm migrating my app using the new component routing approach. I came across the following issue : if I specify the useAsDefault attribute in a route, the rule is correctly applied and I get directed to the expected component. But, if I click on the browser's Back button, it stays on the same page. Looks like it goes back to the previously requested page then the route rule is applied again etc...
I think that the state should be saved in the history with replaceState instead of pushState in case of 'useAsDefault' redirection...
The text was updated successfully, but these errors were encountered: