MudBlazor/MudBlazor

MudDataGrid loses ability to scroll when Sticky is enabled along with Virtualize

Open

#7,709 opened on Oct 30, 2023

View on GitHub
 (5 comments) (1 reaction) (0 assignees)C# (1,631 forks)batch import
bughelp wanted

Repository metrics

Stars
 (10,394 stars)
PR merge metrics
 (Avg merge 6d 6h) (108 merged PRs in 30d)

Description

Bug type

Component

Component name

MudDataGrid

What happened?

Hello,

I have sort of odd issue. When I try to use StickyLeft="true" or StickyRight="true" to any of the PropertyColumn tags along side of attribute Virtualize="true" and ColumnResizeMode="ResizeMode.Container" attributes in MudDataGrid tag, the data grid losses ability to scroll. It is possible to view the issue in Reproduction link

Expected behavior

I expect to scroll over x and y axis when sticky attribute is enabled.

Reproduction link

https://try.mudblazor.com/snippet/GumHlkHkxiLSlkiU

Reproduction steps

  1. Add MudDataGrid component
  2. Add attribute Virtualize, Height, FixedHeader, 'ColumnResizeMode'
  3. Add inside of MudDataGrid component add Columns tag
  4. Add inside of Columns tag few PropertyColumn tags and one of them add attribute StickyLeft or StickyRight
  5. Now you can only navigate via x axis but not via y axis

Relevant log output

No response

Version (bug)

6.11.0

Version (working)

No response

What browsers are you seeing the problem on?

Microsoft Edge

On what operating system are you experiencing the issue?

Windows

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Investigate the interaction between CSS sticky positioning and virtualization in MudDataGrid. Check the rendering logic where sticky columns and virtual scrolling are both enabled, and trace the CSS overflow behavior.
Tech stack
csharp
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBlazor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60