fix: multiple fast navigate calls #20446
Conversation
Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404
|
Easiest way to replicate original issue is to have a hilla layout and 2 flow layouts, setting the network throttling to slow 4g , then navigating to a flow view from a flow view through the layout menu and clicking 2 times on the menu item. |
There was a problem hiding this comment.
We talked with @platosha on Friday, this patch slightly changes how navigation works: with a slow network, when you first time click on the menu link and immediately click on the second one, the application will ignore the second navigation and basically all other navigations until the first one completes.
Maybe it's better to queue these navigations and apply the latest in the end. Flow navigation works like this IIRC.
@platosha promised to see how we can do it.
@caalador do you think it's better to queue like I described?
|
We could push the navigate to The issue is that when the programmer uses react-router |
|
Fix issue where a slow connection
and fast
navigatecalls throwsexception due to faulty blocker
state change.
Fixes #20404