Repository navigation
Vaadin Flow Components V25.2.0-alpha3
Pre-releaseVaadin Flow Components 25.2.0-alpha3
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-alpha2
Changes in All Components
- Chore:
Changes in vaadin-ai-components-flow
-
New Features:
-
⧉ Add OHLC volume series guidance to chart AI tools. PR:9114
_## Summary - Adds LLM guidance for the OHLC/candlestick + volume series pattern to the
update_chart_data_sourcetool description - Instructs the LLM to use_x,_y, and_seriesaliases for the volume query so the series gets proper datetime X values and a name for per-series config matching ### Testing - The fix can be tested using branchfix/chart-ai-controller-candlestick-volume-testBefore:
After:
_ -
⧉ Add 3D chart support with options3d and frame configuration. PR:9093
_## Summary - Add 3D chart support (
options3dandframeconfiguration) to the chart AI tools schema _ -
⧉ Per-series configuration and dual y-axis support. PR:9084
_## Summary - Add per-series configuration support allowing mixed chart types and individual series styling (e.g., one series as column, another as line) - Add dual y-axis support via series-level
yAxisbinding and array-based y-axis configuration schema Part of https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=173099386 Related to #9071 Depends on #9079 _ -
⧉ Add generic plot options schema generation and lookup tool. PR:9079
## Summary - Add
PlotOptionsSchemaGeneratorthat builds JSON schemas for each chart type's plot options at build time, with property descriptions parsed from JavaDoc - AddPlotOptionsSchemaruntime loader andget_plot_options_schematool for LLMs to discover available styling properties - Replace hardcoded plot options inupdate_chart_configurationschema withadditionalPropertiesand dynamic schema lookup - RefactorChartConfigurationParserto use Jackson-basedPlotOptionsdeserialization with Color support, lenient enums, and field-based access Part of https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=173099386 Related to #9071 ---------
-
-
Fixes:
-
⧉ Prevent AIOrchestrator instances from sharing resources. PR:9161
## Summary - Each
LLMProvider, message list, input, file receiver, and controller passed to anAIOrchestratormust be used by at most one orchestrator - Reusing an instance now throwsIllegalStateExceptionFixes https://github.com/orgs/vaadin/projects/103/views/3?pane=issue&itemId=178098791 --------- -
⧉ Match config series to data by name, fall back to position. PR:9142
## Summary - Series configuration templates (names,
plotOptions,yAxis) are matched to data series by name first, with positional fallback for unmatched ones, so LLM-specified legend labels always take effect without swapping data under the wrong labels when SQL returns series in a different order than the config - Previously,applySeriesConfigonly matched by name, which failed for unnamed multi-query series (e.g., candlestick + volume) and for_SERIES-named series where the config used different labels Before:
After:
--------- -
⧉ Resolve unrecognized chart ID to single available chart. PR:9112
## Summary - Fixes
IllegalStateExceptioninChartEntry.getOrCreatewhen the LLM provides an unrecognizedchartId(e.g."1"instead of"chart").resolveChartIdnow validates the provided ID against available charts and falls back to the single available chart when there is exactly one. - Found during a DX test. --------- -
⧉ Avoid NPE in ChartRenderer when chart type is null. PR:9111
_## Summary - Fixes NPE in
ChartRenderer.applyAxisDefaultswhen chart type is not set (data-only update without configuration).Set.of().contains(null)throws NPE; added null guard to treat unset type as default (line chart with category axis). - Found during a DX test. _ -
⧉ Set PlotOptionsFlags on flags data series. PR:9097
_## Summary - When the chart-level type differs from
flags(e.g.column), aDataSeriescontainingFlagItemobjects would not render as flags because it lackedPlotOptionsFlags- AddsapplyFlagsPlotOptions()toChartRendererthat auto-detects flag series by their data items and setsPlotOptionsFlagswhen missing, while preserving any pre-configured plot options _ -
⧉ Add XY series detection to data converter. PR:9095
## Summary - Adds
tryXYpattern toDefaultDataConverterto handle data with_Xand_Ycolumn aliases - Without this, scatter charts and candlestick volume series fall through to the fallback handler which misclassifies columns (dates become category names, second numeric column is ignored) --------- -
⧉ Add missing descriptions to tool parameter schema properties. PR:9087
## Summary - Add descriptions to all tool parameter schema properties in
ChartAIToolsthat were previously missing them, improving the quality of LLM tool-calling by providing clear semantics for each property ---------
-
Changes in vaadin-map-flow
- Fixes:
-
⧉ Register Map resources on the Map element. PR:9134. Ticket:9129
## Description Map uses a custom JSON serializer to automatically register stream resources in the UI when it encounters those during serialization. Currently, those are registered on the UI itself and not on the Map element. This results in access to those resources being denied from the server while a server-side modal is opened. This fixes the serializer to register the stream resources on the map. Thus clients are allowed to access these resources when the map is within a strict modal dialog for example. ## Type of change - Bugfix
-
Changes in vaadin-master-detail-layout-flow
-
Breaking Changes:
-
⧉ Replace ExpandingArea with expandMaster and expandDetail. PR:9156
## Description Follow-up to the web component change vaadin/web-components#11521 Replaces the
expandenum-valued attribute onMasterDetailLayoutwith two independent boolean properties: - Removes theExpandingAreaenum andget/setExpandingAreamethods - AddsisExpandMaster/setExpandMaster(boolean)(defaults tofalse) - AddsisExpandDetail/setExpandDetail(boolean)(defaults tofalse) - Drops theExpandingAreaparameter from the two convenience constructors; callers configure expansion via the new setters Part of vaadin/web-components#11519 ## Type of change - Refactor -
⧉ Remove MasterDetailLayoutVariant. PR:9150
_## Summary - Deletes the
MasterDetailLayoutVariantenum and dropsHasThemeVariant<MasterDetailLayoutVariant>fromMasterDetailLayout. - The sole variantAURA_INSET_DRAWERis being removed from the underlying web component in vaadin/web-components#11503, leaving the Flow-side variant enum with no values, so both it and the mixin are no longer needed. ## Test plan - [x]mvn test -pl vaadin-master-detail-layout-flow-parent/vaadin-master-detail-layout-flowpasses (38/38) - [x]grep -r "MasterDetailLayoutVariant" vaadin-master-detail-layout-flow-parent/→ no matches _
-
-
New Features:
-
⧉ Add setDetailSize overloads with overlaySize parameter. PR:9159
## Description Adds overloads to
setDetailSizethat accept an additional overlay size, so the detail size and overlay size can be configured in a single call:java layout.setDetailSize("300px", "200px"); layout.setDetailSize("300px", true, "200px"); layout.setDetailSize(30, Unit.EM, 20, Unit.EM); layout.setDetailSize(30, Unit.EM, true, 20, Unit.EM);BothStringandfloat/Unitvariants are added, with and without theexpandflag. Each overload delegates to the existingsetDetailSize,setExpandDetail, andsetOverlaySizesetters. Part of vaadin/web-components#11519 ## Type of change - Feature --------- -
⧉ Add setMasterSize/setDetailSize overloads with expand parameter. PR:9157
## Description Adds overloads to
setMasterSizeandsetDetailSizethat accept an additionalexpandboolean, so size and expand can be configured in a single call:java layout.setMasterSize("300px", true); layout.setDetailSize("300px", true);BothStringandfloat/Unitvariants are added for parity with the existing setters. Each overload delegates to the existing size setter andsetExpandMaster/setExpandDetail. Part of vaadin/web-components#11519 ## Type of change - Feature ---------
-
Changes in vaadin-slider-flow
-
Breaking Changes:
-
⧉ Extract
NumberSlider/NumberRangeSlider. PR:9108## Description As a preparation for introducing an integer variant of Slider and Range Slider, this extracts common logic for single value / range value sliders into
NumberSlider/NumberRangeSlider. This moves the min, max and step properties toSliderBaseusing a generic number type. Likewise, the start and end values of range slider values now also use a generic type to facilitate internal logic. As a side effect, all of these now require passing a double literal (10.0,10d) as auto-converting from an integer literal to a boxed double is not supported by Java. Part of #8863 ## Type of change - Breaking change
-
-
New Features:
-
⧉ Add IntegerSlider, IntegerRangeSlider. PR:9123
## Description Adds
IntegerSliderandIntegerRangeSlideras alternative slider variants that use integer values for min, max, step and value properties. Also addsIntegerSliderElementandIntegerRangeSliderElementTestBench elements for convenience. Part of #8863 ## Type of change - Feature ---------
-
Changes in vaadin-spreadsheet-flow
- Fixes:
-
⧉ Prevent infinite focus loop and stale selection in custom editors. PR:9113. Ticket:9036
## Summary - Fix infinite
cellSelectedfeedback loop triggered by programmatic focus changes (e.g.inputElement.select()) inonCustomEditorDisplayedcallbacks - Prevent delayed server responses from hijacking the cell selection when the user has already navigated away, including via keyboard navigation through cells with custom editors - Add server-side reentrancy guard to prevent recursiveonCustomEditorDisplayedcalls when callback code callsrefreshCells()## Root causeCustomEditorEventListener.ONFOCUSunconditionally sentcellSelectedto the server and updated the client-side selection on every focus event — including programmatic focus frominputElement.select()called inonCustomEditorDisplayed. When the callback had non-trivial processing time, the delayed response would steal focus and selection from whatever cell the user had since navigated to, and could trigger an infinite client→server→client loop. ## Approach Client-side (CustomEditorEventListener): trackmousedown/touchstartevents to distinguish user-initiated focus from programmatic focus. Only update the selection and sendcellSelectedfor user-initiated focus. For programmatic focus on a cell the user has already left, return focus to the sheet. Keyboard navigation is unaffected becauseSelectionHandleralready handles selection updates andcellSelectedindependently. Server-side (Spreadsheet): reentrancy guard (insideCustomEditorCallback) onloadCustomEditorOnSelectedCell()to prevent recursiveonCustomEditorDisplayedcalls when user code in the callback callsrefreshCells(). ## Test plan - [ ]CustomEditorIT#comboBoxEditorWithSelect_clickCell_callbackFiredOnce— verifies single click triggers exactly 1 callback (no loop) - [ ]CustomEditorIT#comboBoxEditorWithSelect_switchBetweenCells_noInfiniteLoop— rapidly clicks through editor cells to a non-editor cell, verifies selection stays on the final cell and callback count is bounded - [ ] All 26 existingCustomEditorITtests pass (keyboard navigation, Tab, Shift+Tab, F2, Enter, ESC, shared editors, frozen panes, always-visible mode) --------- -
⧉ Add exception handling around SpreadsheetComponentFactory callbacks. PR:9101
## Description Wrap factory method calls in loadRangeComponents() and loadCustomEditorOnSelectedCell() with try-catch blocks so that a bug in a user-implemented SpreadsheetComponentFactory does not crash the entire spreadsheet. Exceptions are logged at WARN level with the cell address for debugging. Also removes stale null checks on the customComponents set, which is always initialized to an empty HashSet since #9080.
-
Compatibility
- This release use Web Components listed in Vaadin Platform 25.2.0-alpha3
- Tested with Vaadin Flow version 25.2.0-alpha6