Is it possible to completely remove all styling from all input components?

[slepmog]

The bare Blazor looks great in the presentations, but is a nightmare to use for real applications. It simply doesn't have the most basic features such as binding a number with a specific format (e.g. "0.00"), and the workarounds happily provided in the documentation both require ridiculous code duplication and are incompatible with attribute-based data validation.

MudBlazor addresses these concerns and its input controls do exactly the right thing, which is great.
MudBlazor, however, comes with the Material look seemingly nailed to it, which is way less great.

Is there a sane, supported way to completely remove all visuals from all MudBlazor controls whatsoever?
So that the wonderful and very much wanted binding functionality remains, but all the textboxes and the checkboxes and the radio buttons look exactly how the browser would draw them in the absence of any styles?

[danielchalmers]

I think that would be difficult and probably unrealistic but there are some tricks like looking for every class that contains the word "mud" and unsetting their styles:

[class*="mud"] {
  all: unset !important;
}

🤷

[slepmog]

This may be a start, but it unsets too much. The inputs begin to look like labels.

Which may not be of importance to begin with because it's come to my attention that MudBlazor claims the entirety of the project's css. It resets fonts, colors and appearances of everything, well outside of its mud space. Completely unrelated areas of the app become screwed up when I simply include MudBlazor.min.css (which I didn't originally do). This approach does not work for me at all.

[Anu6is]

The library, by design, is an opinionated UI library. While it does offer customization options, those options come with the expectation of still sticking within the material design specs. There really is no simple workaround for stripping the intended core styling of the components.