---

This section details on the original issue you should resolve

<issue_title>v9: Remove deprecated MudGlobal theming properties</issue_title>
<issue_description>Follow-up to: #11415

Summary

Complete the removal of theming-style properties exposed via MudGlobal (e.g., Rounded, Square, Color, Variant, Margin, etc.) that were deprecated in #11415. Ship their final removal in v9.0.0 after carrying deprecation notices in the last v8 minors.

This issue proposes the scope, rationale, migration plan, and release timeline.

---

Why this is necessary

1. Maintainability & surface area

   • MudGlobal accrued parameter mirrors for many components. Keeping global counterparts in sync with component parameters multiplies API surface and review burden across new components and changes.

2. Bug prevention

   • We’ve already seen regressions and inconsistent visual states triggered by global defaults (e.g., Setting the MudGlobal button variant breaks the appearance of other controls #10909, MudDataGridPager - style not correct if MudGlobal.InputDefaults.Variant = Variant.Outlined; #11815). The pattern encourages broad overrides that accidentally affect unrelated controls.

3. Design intent & predictability

   • Material’s guidance favors situational variants per component/purpose. Wide, app-level defaults make component appearances less predictable and harder to reason about in complex UIs.

4. Clear responsibility boundaries

   • Behavioral/back-end flags can live centrally; visual appearance belongs in component parameters, theming tokens, and CSS. Mixing them in MudGlobal led to awkward logic and #pragma noise across the codebase.

5. Performance & code noise

   • The “read-from-global-or-parameter” branches show up across many hot paths. Removing them simplifies rendering and drops warning suppressions/obsolete plumbing sprinkled throughout files.

6. Expectation setting

   • MudGlobal has been documented as experimental. Users have had visible deprecation warnings since MudGlobal: Deprecate theming properties #11415; moving to removal honors that communicated plan and avoids carrying tech debt.

---

Scope

• Remove all theming / appearance properties from MudGlobal and associated indirections:

  • Examples (not exhaustive): Rounded, Square, default Color, default Variant, default Margin, etc.

• Delete any code paths that read these properties or “default to MudGlobal if unset”.

• Remove #pragma and [Obsolete] scaffolding introduced by MudGlobal: Deprecate theming properties #11415.

• Keep non-theming/behavioral globals (if any) that don’t govern visual appearance (to be enumerated below).

Deliverable: a checklist enumerating each removed property & component touch points (see Acceptance Criteria).

---

Replacement guidance (migration)

1) Prefer component parameters where appropriate

<!-- Before -->
<MudTextField Label="Email" />

<!-- After (explicit, discoverable) -->
<MudTextField Label="Email" Variant="Outlined" Margin="Dense" />

2) Use the theme system for shared styling

• Encode defaults via theme tokens (colors/typography/shape) and CSS for cross-cutting polish.
• When many instances must share the same look, wrap with small app-specific components:

@* AppTextField.razor *@
<MudTextField Variant="Outlined" Margin="Dense" Class="app-input @Class" @attributes="AdditionalAttributes" />

@code {
    [Parameter] public string? Class { get; set; }
    [Parameter(CaptureUnmatchedValues = true)] public IDictionary<string, object>? AdditionalAttributes { get; set; }
}

---

Release timeline

• v8.13 / v8.14 (already discussed on the PR): Ship deprecation notices so consumers get compile-time warnings with clear messages and upgrade links.
• v9.0.0: Remove the properties and all bridging code.

Rationale: keeps v8 minors warning-only, gives users one full minor cycle to migrate, and lets v9 drop the obsolete scaffolding.
</issue_description>

Comments on the Issue (you are @copilot in this section)