vaadin/flow 24.3.5

Vaadin Flow 24.3.5

on GitHub

Changes since 24.3.4

All changes

Fixes

• Fix Spring Boot's deprecation warning (#18643)
  Commit · Pull request

  Fixed Spring Boot's deprecation warning affecting SpringComponent.

• Add a lang attribute to the html tag of the browser-too-old.html (#18615)
  Commit · Pull request · Issue

  Specify a lang attribute so a screen reader doe not assume that the page is in the default language that the user chose when setting up the screen reader.

• Remove caching of AppShellConfigurator classes to fix injection (#18603)
  Commit · Pull request · Issue

• Close streams fetched from data-providers (#18552)
  Commit · Pull request · Issue

  Unclosed streams might still leak from the DataView API, that should be fixed in each component using that API.

• Include translation files in Spring native compile hints (#18547)
  Commit · Pull request · Issue

• Consider local npm packages in bundle validation (#18368)
  Commit · Pull request · Issue

  If a project package.json contains references to local npm pacakges instead of parsable version, the bundle validation fails. This change update the version check in bundle validation to accept also local packages. For those packages, a bundle re-creation is triggered only if the reference in package.json does not match the one in the stats.

• Allow moving node to another tree after removeFromTree call (#18486)
  Commit · Pull request · Issue

  Enables moving a component to another UI by just calling Element.removeFromTree() and then adding the component to the other UI. ---------

• Binder validation fixes (#18535)
  Commit · Pull request · Issues 18163, 4988, 17515

  Changes: - Once Binder.handleFieldValueChange runs for a binding when readBean was used, the whole binder will be silently validated also. BinderValidationStatusHandler is called like before (only contains status from changed binding), but StatusChangeEvent is now fired considering all bindings and if possible bean validators as well. - Once Binder.handleFieldValueChange runs for a binding when setBean was used, doWriteIfValid will validate all bindings, not only the changed ones. This prevents writing an invalid bean in cases where one or more of the initial values are in invalid state (but not marked as such since setBean resets validation status), but they have not been changed from their initial value(s). Calling setAsRequiredEnabled with a changed value no longer triggers validation, since that validation is now handled elsewhere when needed as stated above. Minor Javadoc fixes, trying to align Javadocs with code.