Skip to content

Vaadin Flow Components V24.10.0-alpha1

Choose a tag to compare

@vaadin-bot vaadin-bot released this 29 Jan 12:53
· 71 commits to 24.10 since this release
aea6b27

Vaadin Flow Components 24.10.0-alpha1

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 24.9.9

Changes in All Components

  • Chore:
    • ⧉ Increase Web-Component version

Changes in vaadin-grid-flow

  • Fixes:
    • ⧉ TreeGrid children not showing after quick expand/collapse (24.9) [0.5 days] (#8488). PR:8554. Ticket:21731

      When a TreeGrid node was expanded and then collapsed before data arrived from a slow data provider, subsequent expansion attempts would show no children. This was caused by the grid's sub-cache retaining a size of 0 from the cancelled request. The fix removes the sub-cache when collapsing an item with pending requests, allowing fresh data to be fetched on re-expand. ---------

Changes in vaadin-spreadsheet-flow

  • New Features:

    • ⧉ Allow customizing Spreadsheet via part names and css properties (#8228). PR:8537
    • ⧉ Make Action#setIcon(Icon) public (#8515). PR:8538
  • Fixes:

    • ⧉ Show custom editors for merged cells (#8544). PR:8557

    • ⧉ Call numberFormatter from point object (#8489). PR:8494. Ticket:8487

      Replace a call of Highcharts.numberFormat with a call to the numberFormatter method present in the charts object. Previous code assumed that the Highcharts object was globally available to work, which is not the case anymore. ---------

    • ⧉ Update resources map on Spreadsheet client (#8437). PR:8441. 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.

Compatibility

  • This release use Web Components listed in Vaadin Platform 24.10.0-alpha1
  • Tested with Vaadin Flow version 24.9.11