-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Javascript error: Invalid blocker state transition #20404
Comments
This might be connected: https://github.com/vaadin/copilot-internal/issues/3247 |
This looks like a misconfiguration or misusing of React's blocker function in Flow.tsx (ReactRouter/Flow integration). |
To me, this error looks like connected to the |
Exactly, this was what I meant. |
Maybe a check is missing here in the flow/flow-server/src/main/resources/com/vaadin/flow/server/frontend/Flow.tsx Lines 405 to 413 in c4db041
|
I guess the main issue here is that the sample layout uses |
Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: caalador <mikael.grankvist@vaadin.com> Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
* fix: multiple fast navigate calls Fix issue where a slow connection and fast `navigate` calls throws exception due to faulty blocker state change. Fixes #20404 * Queue new navigations during ongoing navigation. * fix blocker nav for basepath Add test view for manual testing. Test script doesn't fail on double click. * Remove test class and selenium dependency. --------- Co-authored-by: caalador <mikael.grankvist@vaadin.com> Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
This ticket/PR has been released with Vaadin 24.5.6. |
This ticket/PR has been released with Vaadin 24.4.19. |
Description of the bug
When I'm navigating in my Vaadin application I have some javascript errors.
Expected behavior
A javascript error should not appear in a normal case of usage.
Minimal reproducible example
Create a Vaadin application with two views in a menu, clicks multiple times on the menu.
I think the error appears when you click on the menu when the application is already navigating so if the view is really fast to load you need to click fast.
Versions
The text was updated successfully, but these errors were encountered: