Please consider adding a pluggable runtime localization provider for Telerik UI for Blazor, primarily targeting Blazor WebAssembly scenarios.

This request is not critical for ASP.NET MVC / Razor / Blazor Server, where IDisplayMetadataProvider already provides a valid extensibility point for custom localization. However, Blazor WebAssembly has no equivalent mechanism, which creates a significant limitation.

Problem (Specific to Blazor WebAssembly)

In Blazor WebAssembly:

• DisplayAttribute is static and reflection‑based
• It cannot use DI, async logic, tenant context, or database access
• MVC metadata extensions such as IDisplayMetadataProvider are not available

As a result, Telerik components can only resolve UI text via:

• DisplayAttribute
• .resx resources

This makes it impossible to integrate:

• Database‑driven localization
• Multi‑tenant localization
• User‑editable translations
• Runtime language switching

Why This Matters

In modern Blazor WebAssembly (SPA) applications, localization is often:

• Runtime‑resolved
• Backed by a database
• Tenant‑ and user‑aware

Other libraries already support this model through pluggable localization providers.
A good example is FluentValidation, which allows localization logic to be resolved at runtime via DI, including custom providers and non‑resource‑based implementations.

References:

• FluentValidation – Localization documentation:
  https://docs.fluentvalidation.net/en/latest/localization.html
• FluentValidation – Custom language manager / provider implementation:
  https://github.com/FluentValidation/FluentValidation/blob/main/docs/localization.md

Because Telerik UI for Blazor does not expose a similar extensibility point, developers are forced to manually specify labels, headers, and enum texts throughout the UI, losing the benefits of automatic localization.

Suggested Direction

Introduce an optional localization provider that Telerik components can use when resolving UI text:

• Keep full backward compatibility with DisplayAttribute
• Enable advanced runtime‑based localization scenarios in Blazor WebAssembly where static attributes are insufficient

This would significantly improve Telerik UI’s suitability for enterprise and multi‑tenant Blazor WASM applications, without impacting existing server‑side solutions.