Skip to content

Vaadin Flow Components V25.2.0-alpha5

Pre-release
Pre-release

Choose a tag to compare

@vaadin-bot vaadin-bot released this 30 Apr 11:05
· 714 commits to main since this release
773610f

Vaadin Flow Components 25.2.0-alpha5

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-alpha4

Changes in vaadin-ai-components-flow

  • Fixes:
    • ⧉ Keep orchestrator usable after a sync failure. PR:9213

      ## Description After a synchronous failure during prompt processing, the orchestrator can get permanently stuck, the subsequent prompts can be logged as "Ignoring prompt: another request is already in progress" and silently dropped. The isProcessing flag is only reset by streamResponseToMessage's doFinally, which is registered on the Reactor subscription. If processUserInput throws before the subscription is wired (e.g. when an AttachmentSubmitListener throws) doFinally never fires and the flag stays stuck. This PR wraps processUserInput in a try/catch that resets the flag and re-throws. The original exception still propagate to the caller, but the orchestrator stays usable so a retry once the dependency recovers actually reaches the provider. ## 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.

    • ⧉ Detect silent abort after tool calls. PR:9212

      ## Description Follow-up to #9195. That previous fix catches a streaming response that ends without any finish_reason. But it misses a related case: a tool-using exchange where the first roundtrip succeeds (emitting tool calls and a finish_reason) but the follow-up roundtrip silently aborts. The check is sticky: once a real terminal chunk has been observed, trailing metadata-only chunks (e.g. OpenAI's streamUsage trailer with empty choices and usage stats) cannot flip the gate back. This PR widens the check to track whether any chunk in the stream represented a terminal model state — a chunk that has a finish_reason and no pending tool calls. Pending tool calls mean Spring AI is going to make another roundtrip, so a chunk with them is intermediate even if it has a finish_reason. The signal is a logged warning rather than a thrown error. The heuristic cannot enumerate every provider quirk across vendors and configurations, so a false positive must not surface as a user-visible failure on a valid response. Developers retain observability via logs; if responses appear truncated, the warning is the signal. ## 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-menu-bar-flow

  • Fixes:
    • ⧉ Propagate menu-bar item tooltip to connector items. PR:9216

      ## Description The new MenuBarTooltipController in @vaadin/menu-bar 25.2.0-alpha9 (introduced in vaadin/web-components#11586) short-circuits in setTarget when the target's item has no tooltip property — it clears the target and closes the tooltip immediately. Flow's connector built items without a tooltip field (tooltip text was only stored on the wrapper component and read via a custom generator), so menu-bar tooltips never opened. menubarConnector.js so the controller's gating check recognizes the item as having a tooltip. The existing custom generator continues to read the live value from item.component.tooltip, so updates via setTooltipText still display the latest text. Verified MenuBarTooltipIT passes (3/3) against local web-components at main. ## Type of change - Bugfix ---------

Changes in vaadin-popover-flow

  • New Features:
    • ⧉ Add setTabFocusEnabled API to Popover. PR:9208

      ## Summary Related to vaadin/web-components#11423 - Adds Popover#setTabFocusEnabled(boolean) / isTabFocusEnabled() to the Flow wrapper, mapping to the web component's noTabFocus property in positive form (default true, matching the web component's default of noTabFocus = false). - When set to false, pressing Tab on the target/sibling skips past the popover and Shift+Tab does not move focus into the popover's last focusable. Has no effect on modal popovers (which use their own focus trap), as documented in the Javadoc. - Mirrors the existing inverted-boolean pattern used for setCloseOnEsc / setCloseOnOutsideClick. ## Test plan - [x] Unit test PopoverTest#setTabFocusEnabled_isTabFocusEnabled covers the default state and toggling in both directions, asserting both the public getter and the underlying noTabFocus element property. - [x] mvn spotless:apply clean. - [x] mvn test -pl vaadin-popover-flow-parent/vaadin-popover-flow -Dtest='PopoverTest' passes. 🤖 Generated with Claude Code

Compatibility