This was answered by the MudBlazor team stating that it's related to a bug that has already been fixed and planned for release. Using a previous version is the current solution until the next release.