fix: render vue components in top frozen rows - #5268
Merged
fangsmile merged 1 commit intoAug 5, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤔 这个分支是...
🔗 相关 issue 连接
close #5265
💡 问题的背景&解决方案
顶部冻结数据行位于顶部冻结区域,但 Vue DOM 自定义布局此前仍使用 body 容器,导致组件挂载到错误的覆盖层并显示为空白。
本次修改补充了顶部冻结行的容器路由:
headerDomContainerfrozenHeaderDomContainerrightFrozenHeaderDomContainer底部冻结行的现有判断优先级保持不变,并新增三个回归场景覆盖上述容器映射。
📝 Changelog
☑️ 自测
验证结果:
npm test -- --runInBand vue-stable-id.test.ts:11/11 通过npm run compile:通过rush build -t @visactor/vue-vtable:通过,存在仓库既有构建 warningrush change --verify --target-branch upstream/develop --no-fetch:通过正常 push 触发的全量 pre-push 测试中,
vue-vtable11/11、vtable274/274、vtable-plugins64/64、vtable-gantt25/25 均通过。未改动的vtable-sheet包存在既有失败,主要为@visactor/vtable-plugins/@visactor/vtable-gantt模块解析问题,另有两个公式错误处理断言差异;本次差异不涉及该包。