-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Paging Ui Example positions column values incorrectly #298
Comments
Link to demo page: https://brave-cliff-0c0c93310.azurestaticapps.net/DataGrid |
vnbaaij
added a commit
that referenced
this issue
Jan 26, 2023
DemoSection: add AdditionalFiles parameter DataGrid: Fix #298
Check fixed version here: https://brave-cliff-0c0c93310-302.centralus.azurestaticapps.net/DataGrid |
vnbaaij
added a commit
that referenced
this issue
Jan 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悰 Bug Report
On the Blazor fast demo page under the Datagrid examples exists a Custom paging UI Example.
Inside the example the number of the pages inside the Datagrid is displayed as buttons.
When accessing the data on another page the the positions of column values are incorrect. All column values are displayed on the far right and squished together.
馃捇 Repro or Code Sample
The code snipped are copied from the demo page:
Razor:
CSS:
馃 Expected Behavior
The column values should be aligned with the column title.
馃槸 Current Behavior
When the page in the Datagrid is changed the values in the column are no longer aligned with column title and are squished together on the right side of the Datagrid .
馃敠 Context
When changing the page inside the Datagrid the displayed row values are squished together and for multiple rows. It makes it more difficult to associate the values to their respective rows and makes the data harder to read and use the information.
馃實 Your Environment
Windows 11
net6.0 framework
visual studio 2022
Microsoft Edge latest version
The text was updated successfully, but these errors were encountered: