Vaadin Flow 24.5.12

Changes since 24.5.11

All changes

Fixes

• Fix UI refresh event name (#20921)
  Commit · Pull request · Issue

  The name used to register the event listener for hotswap refresh and the name used to fire the event are different. This change fixes the name in the listener.

• Build service worker without writing it to FS (#20909)
  Commit · Pull request

• Support bun 1.2 lock file (#20900)
  Commit · Pull request

• Trigger refresh from client on hotswap with PUSH (#20848)
  Commit · Pull request · Issue

  When PUSH is enabled, Flow Hotswapper uses it to refresh only the affected UIs. However, this can cause issues if Flow views contain code that relies on VaadinRequest thread local, since hotswap refresh start in a background thread. This change defines a client side event listener to trigger the refresh, and uses PUSH only to fires the event.

• Fix setReadonly when using binder with records (#20855)
  Commit · Pull request · Issue

  When Binder is used with record, calling setReadonly method does not have any effect because the logic only considers bindings with a proper setter. This change fixes the setReadonly logic to take care of all bindings when Binder is using a record.

Code refactoring

• Use Vite official API for building sw.js (#20894)
  Commit · Pull request

Vaadin Flow 24.7.0.alpha9

Changes since 24.7.0.alpha8

All changes

Fixes

• Fix UI refresh event name
  Commit · Pull request · Issue

  The name used to register the event listener for hotswap refresh and the name used to fire the event are different. This change fixes the name in the listener.

Vaadin Flow 24.6.4

Changes since 24.6.3

All changes

Fixes

• Fix UI refresh event name (#20921)
  Commit · Pull request · Issue

  The name used to register the event listener for hotswap refresh and the name used to fire the event are different. This change fixes the name in the listener.

Vaadin Flow 24.7.0.alpha8

Changes since 24.7.0.alpha7

All changes

New features

• Add accessibleDisabledButtons feature flag
  Commit · Pull request

Fixes

• Build service worker without writing it to FS
  Commit · Pull request

• Support bun 1.2 lock file
  Commit · Pull request

• Trigger refresh from client on hotswap with PUSH
  Commit · Pull request · Issue

  When PUSH is enabled, Flow Hotswapper uses it to refresh only the affected UIs. However, this can cause issues if Flow views contain code that relies on VaadinRequest thread local, since hotswap refresh start in a background thread. This change defines a client side event listener to trigger the refresh, and uses PUSH only to fires the event.

• Set viewport-fit=cover to enable CSS env() variables in PWAs
  Commit · Pull request · Issue

  Using env() variables in PWAs requires viewport-fit=cover to be set in the . Without this setting, some parts of such components as app-layout get cut off on iOS devices. Adding viewport-fit follows MDN's documentation about env() variables and helps fix such issues .

Code refactoring

• Use Vite official API for building sw.js
  Commit · Pull request

Vaadin Flow 24.6.3

Changes since 24.6.2

All changes

Fixes

• Build service worker without writing it to FS (#20909)
  Commit · Pull request

• Support bun 1.2 lock file (#20900)
  Commit · Pull request

• Trigger refresh from client on hotswap with PUSH (#20848)
  Commit · Pull request · Issue

  When PUSH is enabled, Flow Hotswapper uses it to refresh only the affected UIs. However, this can cause issues if Flow views contain code that relies on VaadinRequest thread local, since hotswap refresh start in a background thread. This change defines a client side event listener to trigger the refresh, and uses PUSH only to fires the event.

• Set viewport-fit=cover to enable CSS env() variables in PWAs (#20836)
  Commit · Pull request · Issue

  Using env() variables in PWAs requires viewport-fit=cover to be set in the . Without this setting, some parts of such components as app-layout get cut off on iOS devices. Adding viewport-fit follows MDN's documentation about env() variables and helps fix such issues .

• Navigate with full url (#20846)
  Commit · Pull request · Issue

  for instance when adding a query parameter at the end.

• Fix setReadonly when using binder with records (#20855)
  Commit · Pull request · Issue

  When Binder is used with record, calling setReadonly method does not have any effect because the logic only considers bindings with a proper setter. This change fixes the setReadonly logic to take care of all bindings when Binder is using a record.

• Store the exception and not an array with the exception for uncaught promise exceptions (#20840)
  Commit · Pull request

Code refactoring

• Use Vite official API for building sw.js (#20894)
  Commit · Pull request

Vaadin Flow 24.7.0.alpha7

Changes since 24.7.0.alpha6

All changes

New features

• DisabledUpdateMode for ShortcutRegistration
  Commit · Pull request

Fixes

• Navigate with full url
  Commit · Pull request · Issue

  for instance when adding a query parameter at the end.

Vaadin Flow 24.7.0.alpha6

Changes since 24.7.0.alpha5

All changes

New features

• Queue message payloads
  Commit · Pull request · Issue

  Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout format server clear queue for push messaging.

• Add interfaces for CRUD services
  Commit · Pull request · Issue

  Similar interfaces were previously in Hilla but are equally useful in Flow applications

Fixes

• Fix setReadonly when using binder with records
  Commit · Pull request · Issue

  When Binder is used with record, calling setReadonly method does not have any effect because the logic only considers bindings with a proper setter. This change fixes the setReadonly logic to take care of all bindings when Binder is using a record.

• Make route config errors more prominent
  Commit · Pull request · Issue

  When route configuration errors happen, make sure to output the actual error message as the first output at ERROR level. When this is detected at startup, we can't prevent printing out the stack trace too since the container does that when initialization throws. Also checked all the messages for different route misconfiguration cases, and they seem to be fine.

• Store the exception and not an array with the exception for uncaught promise exceptions
  Commit · Pull request

Vaadin Flow 24.7.0.alpha5

Changes since 24.7.0.alpha4

All changes

New features

• Add support for OAuth2 logout configuration
  Commit · Pull request · Issue

  Improves setOAuth2LoginPage method in order to configure an OIDC logout succes shandler capable of handling redirection for UIDL requests. Post logout URL is by default the application root, but a method overload allows to specify a custom URL.

Fixes

• Validate downloaded node
  Commit · Pull request · Issue

  Validate downloaded node against the provided sha256 hash.

• Remove broken node archive
  Commit · Pull request

  If archive extraction throws remove arcive to next time re-download. In cases where the archive can be corrupt remove file.

Vaadin Flow 24.7.0.alpha4

Changes since 24.7.0.alpha3

All changes

New features

• React 19 behind a feature flag
  Commit · Pull request

Fixes

• ReactRouterOutlet interferes with layout
  Commit · Pull request

• Parse bot user agents
  Commit · Pull request · Issue

  Add parsing for byte spider and duck duck bot user agents.

Vaadin Flow 24.6.2

No changes since 24.6.1