Vaadin Flow Components V24.10.7
Vaadin Flow Components 24.10.7
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.10.6
Changes in All Components
- Chore:
- ⧉ Increase Web-Component version
Changes in vaadin-spreadsheet-flow
- Fixes:
-
⧉ Init Spreadsheet api on connect to avoid undefined api in Dialog (#9333) (CP: 24.10). PR:9366
This PR cherry-picks changes from the original PR #9333 to branch 24.10. --- #### Original PR description > When a Spreadsheet is attached inside a closed Dialog and the Dialog later opens, Flow flushes its buffered property writes and
callJsFunctioncalls in the same task. The connector created its api lazily inside Lit's microtask-scheduledupdated(), so the RPC methods ran first — eleven of them threwCannot read properties of undefined, and the initial selection was silently dropped. > >java > Spreadsheet spreadsheet = new Spreadsheet(); > spreadsheet.setSelectionRange(2, 7, 7, 10); > Dialog dialog = new Dialog(); > dialog.add(spreadsheet); > dialog.open(); // console floods with errors, selection not applied >> > The api is now created eagerly inconnectedCallback(Lit 3 sets uprenderRootinsuper.connectedCallback()), and each RPC method callsperformUpdate()at the top so pending property writes have propagated to the api before it's used. > > One symptom remains structurally async: GWT schedules the initialrelayout()viasetTimeout(1ms), so the sheet widget's layout state isn't yet populated when the firstsetSelectedCellAndRangearrives. That call would dereferencedefinedRowHeightsand throw inside\$scrollAreaIntoView. Flow reissuessetSelectedCellAndRangeafter the spreadsheet has fully attached, so the connector skips the first call when the layout state isn't ready and lets the second one apply the selection. > > --- > > 🤖 Generated with Claude Code ---------
-