As part of the Multi-Body Grid architecture, we need to ensure that the Left (locked: 'start') and Right (locked: 'end') SubGrids can be detached from the main window and rendered in separate popup windows, similar to the LivePreview component.
Requirements:
- Encapsulation: SubGrids must be fully functional even when not physically adjacent in the same DOM tree.
- Window Connect/Disconnect Logic: Implement logic (likely on the Grid Container) to handle moving a SubGrid instance into a newly spawned window and recovering it when the window closes.
- Data Continuity: Ensure the App Worker maintains the single source of truth for the
Store and SelectionModel regardless of which window the VDOM is projected into.
- Keyboard navigation across windows (carried from #9496 on 2026-11-06, when that epic closed with its single-window requirements delivered): arrow navigation must keep working when the
locked: 'start' SubGrid has been ripped out into its own window. The worker side already holds: CellModel#onNavKeyColumn steps through the logical dataFields of every region and selects by View#getLogicalCellId. What remains is routing the detached window's key events into the same SelectionModel once detachment exists.
As part of the Multi-Body Grid architecture, we need to ensure that the Left (
locked: 'start') and Right (locked: 'end') SubGrids can be detached from the main window and rendered in separate popup windows, similar to theLivePreviewcomponent.Requirements:
StoreandSelectionModelregardless of which window the VDOM is projected into.locked: 'start'SubGrid has been ripped out into its own window. The worker side already holds:CellModel#onNavKeyColumnsteps through the logicaldataFieldsof every region and selects byView#getLogicalCellId. What remains is routing the detached window's key events into the sameSelectionModelonce detachment exists.