Skip to content

Vaadin Flow Components V25.2.0-alpha6

Pre-release
Pre-release

Choose a tag to compare

@vaadin-bot vaadin-bot released this 11 May 13:42
· 699 commits to main since this release
ffd20aa

Vaadin Flow Components 25.2.0-alpha6

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.2.0-alpha5

Changes in All Components

  • Chore:
    • ⧉ Increase Web-Component version

Changes in vaadin-ai-components-flow

  • Fixes:
    • ⧉ Fire response complete on empty responses. PR:9215

      ## Description A turn that produces no visible text — typically a tool-only turn where the model emits tool calls and stops without commentary — is still a successful exchange. But the response-complete lifecycle hooks were skipped: both the application-facing ResponseCompleteListener.onResponseComplete and the controller-facing AIController.onResponseComplete were gated behind a non-empty-text check. Controllers that flush their pending UI state in onResponseComplete (e.g. ChartAIController applying its pending query) never render on these turns; application listeners miss the completion entirely. This PR moves both hook invocations out of the non-empty-text gate so every successful exchange fires them, with the firing cadence unchanged (still once per user prompt, not per tool call or round-trip). The conversationHistory add stays gated to avoid polluting history with empty assistant entries. ## Type of change - [x] Bugfix - [ ] Feature ## Checklist - [x] I have read the contribution guide: https://vaadin.com/docs/latest/contributing/overview - [x] I have added a description following the guideline. - [ ] The issue is created in the corresponding repository and I have referenced it. - [x] I have added tests to ensure my change is effective and works as intended. - [x] New and existing tests are passing locally with my change. - [x] I have performed self-review and corrected misspellings.

Changes in vaadin-combo-box-flow

  • New Features:
    • ⧉ Add collapseChips API to MultiSelectComboBox. PR:9235. Ticket:8533

      The web component side added a collapseChips boolean property to vaadin-multi-select-combo-box. When enabled, all selected-item chips collapse into the overflow chip whenever they don't all fit, instead of showing as many as possible. Without this PR, Flow users have to reach for getElement().setProperty("collapseChips", true) to use the new behavior. The change adds a typed isCollapseChips() / setCollapseChips(boolean) pair on MultiSelectComboBox, mirroring the shape of the existing selectedItemsOnTop API. --- 🤖 Generated with Claude Code

Changes in vaadin-context-menu-flow

  • Breaking Changes:
    • ⧉ Add tooltip APIs to context-menu and menu-bar items. PR:9223. Ticket:10415

      Adds Flow APIs for menu item tooltips, building on web-component support added in vaadin/web-components#11549. A single <vaadin-tooltip> is slotted into the menu/context-menu and auto-attached on first use, shared across root and sub-menu items. The menu-bar connector recurses through the item tree so tooltip and tooltipPosition reach nested items, which the web component's tooltip controller picks up. The previous MenuBar#setTooltipText(MenuItem, String) API is deprecated in favor of the new item-level methods and scheduled for removal in Vaadin 26. ## Examples Set a tooltip on any menu item via setTooltipText / setTooltipPosition: java MenuBar menuBar = new MenuBar(); MenuItem save = menuBar.addItem("Save"); save.setTooltipText("Save changes"); save.setTooltipPosition(TooltipPosition.BOTTOM); Convenience addItem overloads accept the tooltip text directly: java MenuBar menuBar = new MenuBar(); menuBar.addItem("Save", "Save changes", e -> save()); menuBar.addItem(new Icon(VaadinIcon.TRASH), "Delete selected", e -> delete()); Same APIs on ContextMenu (and GridContextMenu) items, including nested sub-menu items: java ContextMenu contextMenu = new ContextMenu(target); MenuItem edit = contextMenu.addItem("Edit", "Edit this row"); SubMenu more = contextMenu.addItem("More").getSubMenu(); more.addItem("Duplicate", "Create a copy"); more.addItem("Archive").setTooltipText("Move to archive"); > [!WARNING] > New tooltip-aware addItem overloads may make existing call sites ambiguous when a null listener is passed with a cast, e.g.: > > java > foo.getSubMenu().addItem("bar", > (ComponentEventListener<GridContextMenuItemClickEvent<Object>>) null); > > > Such call sites need to be updated to disambiguate the overload. --- 🤖 Generated with Claude Code ---------

Changes in vaadin-grid-flow

  • Breaking Changes:
    • ⧉ Add tooltip APIs to context-menu and menu-bar items. PR:9223. Ticket:10415

      Adds Flow APIs for menu item tooltips, building on web-component support added in vaadin/web-components#11549. A single <vaadin-tooltip> is slotted into the menu/context-menu and auto-attached on first use, shared across root and sub-menu items. The menu-bar connector recurses through the item tree so tooltip and tooltipPosition reach nested items, which the web component's tooltip controller picks up. The previous MenuBar#setTooltipText(MenuItem, String) API is deprecated in favor of the new item-level methods and scheduled for removal in Vaadin 26. ## Examples Set a tooltip on any menu item via setTooltipText / setTooltipPosition: java MenuBar menuBar = new MenuBar(); MenuItem save = menuBar.addItem("Save"); save.setTooltipText("Save changes"); save.setTooltipPosition(TooltipPosition.BOTTOM); Convenience addItem overloads accept the tooltip text directly: java MenuBar menuBar = new MenuBar(); menuBar.addItem("Save", "Save changes", e -> save()); menuBar.addItem(new Icon(VaadinIcon.TRASH), "Delete selected", e -> delete()); Same APIs on ContextMenu (and GridContextMenu) items, including nested sub-menu items: java ContextMenu contextMenu = new ContextMenu(target); MenuItem edit = contextMenu.addItem("Edit", "Edit this row"); SubMenu more = contextMenu.addItem("More").getSubMenu(); more.addItem("Duplicate", "Create a copy"); more.addItem("Archive").setTooltipText("Move to archive"); > [!WARNING] > New tooltip-aware addItem overloads may make existing call sites ambiguous when a null listener is passed with a cast, e.g.: > > java > foo.getSubMenu().addItem("bar", > (ComponentEventListener<GridContextMenuItemClickEvent<Object>>) null); > > > Such call sites need to be updated to disambiguate the overload. --- 🤖 Generated with Claude Code ---------

Changes in vaadin-menu-bar-flow

  • Breaking Changes:
    • ⧉ Add tooltip APIs to context-menu and menu-bar items. PR:9223. Ticket:10415

      Adds Flow APIs for menu item tooltips, building on web-component support added in vaadin/web-components#11549. A single <vaadin-tooltip> is slotted into the menu/context-menu and auto-attached on first use, shared across root and sub-menu items. The menu-bar connector recurses through the item tree so tooltip and tooltipPosition reach nested items, which the web component's tooltip controller picks up. The previous MenuBar#setTooltipText(MenuItem, String) API is deprecated in favor of the new item-level methods and scheduled for removal in Vaadin 26. ## Examples Set a tooltip on any menu item via setTooltipText / setTooltipPosition: java MenuBar menuBar = new MenuBar(); MenuItem save = menuBar.addItem("Save"); save.setTooltipText("Save changes"); save.setTooltipPosition(TooltipPosition.BOTTOM); Convenience addItem overloads accept the tooltip text directly: java MenuBar menuBar = new MenuBar(); menuBar.addItem("Save", "Save changes", e -> save()); menuBar.addItem(new Icon(VaadinIcon.TRASH), "Delete selected", e -> delete()); Same APIs on ContextMenu (and GridContextMenu) items, including nested sub-menu items: java ContextMenu contextMenu = new ContextMenu(target); MenuItem edit = contextMenu.addItem("Edit", "Edit this row"); SubMenu more = contextMenu.addItem("More").getSubMenu(); more.addItem("Duplicate", "Create a copy"); more.addItem("Archive").setTooltipText("Move to archive"); > [!WARNING] > New tooltip-aware addItem overloads may make existing call sites ambiguous when a null listener is passed with a cast, e.g.: > > java > foo.getSubMenu().addItem("bar", > (ComponentEventListener<GridContextMenuItemClickEvent<Object>>) null); > > > Such call sites need to be updated to disambiguate the overload. --- 🤖 Generated with Claude Code ---------

Compatibility