Frontmatter
| id | 9620 |
| title | Grid Multi-Body: Fix Null Data Store and Consolidate Loading Mask |
| state | Closed |
| labels | bugaigrid |
| assignees | tobiu |
| createdAt | Apr 1, 2026, 7:36 PM |
| updatedAt | Apr 1, 2026, 9:00 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9620 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | 9486 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 1, 2026, 9:00 PM |
Grid Multi-Body: Fix Null Data Store and Consolidate Loading Mask
Closedbugaigrid

Problem
When locked columns are configured (like the recent DevIndex test),
GridContainerinstantiatesbodyStartandbodyEndbut fails to explicitly pass thestorereference downward. This causes a fatalTypeError: Cannot read properties of nullinsideGridBody.createViewData()when it attempts to evaluate.isLoading.Additionally, loading masks historically target the inner
GridBody. In a Multi-Body layout, this would create fragmented loading spinners across each discrete column body. The mask must be promoted to target the unifiedbodyWrapper.Implementation Plan
bodyStartandbodyEndinstantiation loops to explicitly mapstoreanduseInternalId.isLoadingbehavior so that it masks thebodyWrapperinstead of fragmenting across all three inner bodies.