Vaadin Flow Components V25.0.3

Vaadin Flow Components 25.0.3

This is a release of the Java integration for Vaadin Components to be used from the Java server side with Vaadin Flow.

Changes in Flow Components from 25.0.2

Changes in All Components

• Chore:
  • ⧉ Increase Web-Component version

Changes in vaadin-master-detail-layout-flow

• New Features:
  • ⧉ Add MasterDetailLayoutVariant enum with Aura variant (#8414). PR:8416

Changes in vaadin-messages-flow

• Fixes:

  • ⧉ Add locale fallback for MessageList to handle variants (#8417). PR:8420

  • ⧉ Add locale fallback for MessageList to handle variants. PR:8403

    MessageList now gracefully handles locale variants (e.g., "de-DE-hw") by implementing a progressive fallback strategy when the full locale string is not valid for Intl.DateTimeFormat: 1. Try full locale (e.g., "de-DE-hw") 2. Fall back to base locale (e.g., "de-DE") 3. Fall back to language only (e.g., "de") 4. Fall back to browser default This prevents the component from crashing when custom locale variants are used for resource bundle customization.

Changes in vaadin-ordered-layout-flow

• Fixes:
  • ⧉ #8408, apply latest used slot, when adding a component using addComponentAtIndex with an index >= size (#8436). PR:8442

Changes in vaadin-spreadsheet-flow

• Fixes:

  • ⧉ Update resources map on Spreadsheet client (#8437). PR:8440. Ticket:8428

  • ⧉ Update resources map on client

    Ensure that the resources map is updated with the new resource URI. When an image is moved away from the viewport, it can be detached and not available in the server anymore if the client side requests it again. Spreadsheet already reloads the image when it is scrolled back into view, but as it was using setProperty to set the resources property in the web component, it didn't trigger the update as Flow didn't detect a change in the property - the resources prop holds the name of the overlays and that indeed doesn't change, only the attribute value related to that resource. Changed by replacing setProperty with executeJs to ensure that Flow will trigger the update in the web component, thus updating the resource map so it will be used by the img element on creation.

Changes in vaadin-upload-flow

• Fixes:
  • ⧉ Allow clearing file list multiple times (#8419). PR:8422

Compatibility

• This release use Web Components listed in Vaadin Platform 25.0.3
• Tested with Vaadin Flow version 25.0.4