Vaadin Flow 24.7.1

Changes since 24.7.0

All changes

New features

• Allow forcing Hotswapper to reload the page (#21157)
  Commit · Pull request · Issue

  By default, on class change, Hotswapper determines the best strategy to refresh the browser page. However, in some situations, a full page reload may be a better option. This change allows forcing Hotswapper to always trigger a full page reload if the vaadin.hotswap.forcePageReload system property is set to true. In addition, the Hotswapper.forcePageReload() method can be called to change the behavior at runtime instead of setting the system property.

Fixes

• Renavigation to same url (#21170)
  Commit · Pull request · Issue

  after initial navigation to same route when using postpone

• Clean file-routes if hilla not in use (#21155)
  Commit · Pull request · Issue

• Add global click handler for navigation (#20990)
  Commit · Pull request · Issue

  When using React router, clicks on anchors are intercepted only if Flow client has been initialized. In Hilla or hybrid application, if a Flow view is never navigated, clicking on such links cause the browser to reload the page instead of navigating to the expected view. This change registers a global click handler that intercepts click events and triggers a router navigation if necessary. The new behavior is aligned with vaadin-router.