vaadin/flow 24.8.0.alpha9 on GitHub

Changes since 24.8.0.alpha8

Prevent resynchronization loop
Commit · Pull request · Issue
Changes pushed to the client during components' attach phase of a resynchronization request can be ignored, triggering a continuous resync cycle. This change adds messages received during resync to the pending messages queue, so that messsages older than the resync request are discarded, whereas messages pushed after server resync are processed when client resync completes. In addition, it prevents asynchronous message sending while the server prepares the UI tree for resynchronization.
Prevent duplicated history entry with vaadin-router
Commit · Pull request · Issues 21243, 19494, 335
When using legacy vaadin-router, browser history for client side navigation is updated by the router itself when navigation completes. However, in some situations the history gets updated also by the server side, causing two history entries for the same navigation and consequently a wrong behavior if pressing browser back button. This change: - Prevents updating history on the server side, unless the server is handling a postponed navigation for which vaadin-router does not update the history - Adds a test module for vaadin-router with the most common navigation tests - Re-enables several tests that are now passing, likely because previous changes fixed the related issues