Conversation
|
As mentioned offline, there are many CSS rules that include They're all broken and will cause bugs. |
Yes, it is indeed a bug in selecting the right assembly to look in. Will be fixed for next build |
I'm setting |
… into vnbaaij/fluentui-411
|
I've addressed most of the issues but would be good to go through a test together to see what needs to be fixed still. We do need to wait for a new version of the v4.11 packages to do so because we had to make some changes on our side as well. |
|
@vnbaaij I've updated to 4.11.1 and fixed a lot more issues. I found one regression with empty rows (see microsoft/fluentui-blazor#3160) |
Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>










Update @JamesNK
4.11.x changes FluentDataGrid to use table/tr/td instead of web components. A lot of custom CSS and JavaScript needs to react to the new elements and attributes in the HTML.
I've been through the app a number of times and tested every page that has grids. It looks ok to me, but I'm sure there are some outstanding issues. I think the best way to find them is merge and have bugs reported about dashboard issues.
Update @vnbaaij
If you'd like to know more about the why behind the FluentDataGrid change, see microsoft/fluentui-blazor#2667
Description
Initial work needed to move to the Fluent UI Blazor 4.11.0 release
(not out yet). This is still in draft.Fixes # (issue)
Checklist
<remarks />and<code />elements on your triple slash comments?breaking-changetemplate):doc-ideatemplate):Microsoft Reviewers: Open in CodeFlow