/* * mudcompat.css — the base look for the compatibility adapters. * * This file replaces MudBlazor.min.css (594 KB, render-blocking, and the first thing a phone on a cold * visit had to finish downloading before it was allowed to paint). It is a fraction of that size because * it covers only the components this platform actually uses, and because everything that can be expressed * as a custom property already is: colour, type scale, elevation and shell metrics all arrive from * MudThemeProvider, which serialises the same TmaTheme.Value as before. * * It is deliberately written against the SAME class names the package used. ~400 first-party rules across * tokens.css, base.css, shell.css, admin.css, app.css and the scoped .razor.css files extend those names * rather than replacing them, and a large part of the test suite asserts through them. Those rules load * after this file and continue to win, which is what makes the swap invisible. * * Ordering note: every rule here is a single class selector (specificity 0,1,0) so that any existing * first-party override, however it is written, still takes precedence. */ /* ---------- element reset --------------------------------------------------------------------- * * The package sheet carried an element reset as well as its components, and dropping it put the * BROWSER'S default button back under every first-party `