vaadin/flow 23.0.8

Vaadin Flow 23.0.8

on GitHub

Changes since 23.0.7

All changes

Fixes

• Fix Vite to use vaadin/bundles on Windows (#13879)
  Commit · Pull request · Issue

• Update Page Title after processing AfterNavigation listeners (#13825)
  Commit · Pull request · Issue

  The page title is updated after afterNavigation invocation and properly updated the title.

• Improve message sender / handler robustness in resync scenarios (#13733)
  Commit · Pull request · Issue

  Process re-sync messages via normal message queue and use semaphore to protect re-sync process (i.e. do not allow other messages while performing re-sync). This PR is adopted from similar fixes for Vaadin 8. vaadin/framework#11791 vaadin/framework#12043 vaadin/framework#12178 This also changes the method forceMessageHandling in a way that the desire to resynchronise is registered before calling endRequest. If this is not done, endRequest may end up sending out a request itself and that then causes the re-sync request to fail because a request is already in flight. This ends up throwing an IllegalStateException at com/vaadin/client/communication/RequestResponseTracker.java.

• Avoid potential slow Set#removeAll call in HierarchicalCommunicator (#13746)
  Commit · Pull request · Issue

• Devmode popup will show Hilla instead of Vaadin in Hilla applications (#13725)
  Commit · Pull request

• Ignore CancellationException for running UI update tasks (#13708)
  Commit · Pull request · Issue

  Ignore CancellationException if the task is cancelled in the meantime.

• Do not serve static resources from dev server if dev server startup failed (#13773)
  Commit · Pull request · Issue

  This happens when the dev server startup fails, i.e. DevModeInitializer.runNodeTasks throws an exception, then "action" in the constructor throws an exception and devServerStartFuture completes with an exception. After this when the browser reloads, it needs to go to AbstractDevModeHandler.handleRequest which checks if an exception happened and sets isDevServerFailedToStart accordingly. However before getting to AbstractDevModeHandler.handleRequest the static file server checks if the requested path is a static resource by calling AbstractDevModeHandler.serveDevModeRequest. This throws an exception because it only checks that the dev server is not still starting and then it tries to access it using port 0.

• Move the clean-frontend phase to be before clean (#13763)
  Commit · Pull request

  Move clean-frontend to pre-clean as if mvn clean is executed before clean-frontend clean will remove the target folder making removal of node_modules fail on windows if there is a symlink to target/flow-frontend touches #13760

• Serialize byte[] as Array (#13656)
  Commit · Pull request

  (cherry picked from commit 53511df)