You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5d8a4c4
Browse filesBrowse the repository at this point in the historyBrowse files
This PR addresses an issue where merged cells in a `TableView` would "unmerge" or break when the first cell of the merge was scrolled into the area overlaid by a pinned row or column.
- Updated `RenderTableViewport` to expand the `_targetLeadingColumnPixel` and `_targetLeadingRowPixel` calculation to include the pinned extent.
- Strengthened the documentation in `TableView` and `TableViewCell` to explicitly state that the same child and merge information **must** be returned from every vicinity in the merge to avoid unmerging when cells are culled due to lazy loading.
Fixesflutter#174862
## Pre-Review Checklist
**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.
[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
0 commit comments