Progress® Telerik® UI for Blazor Feedback Portal
Back to Feed
Request a Feature Report a Bug
Unplanned
Last Updated: 14 May 2026 13:30 by ADMIN
Thomas
Created on: 12 May 2026 20:34
Category: UI for Blazor
Type: Feature Request
1
Runtime Localization Provider enums, property display names and model-driven text for Telerik UI for Blazor WebAssembly

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:

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.

6 comments
ADMIN
Dimo
Posted on: 14 May 2026 13:30

OK, in this case I am confirming the request as "Unplanned".

Thomas
Posted on: 14 May 2026 12:37
When I look at your source you are internaly acctualy using a kind of provider to return strings for enum and model propeties. This internal provider uses the DisplayAttribute. It sould be very easy for you expose this provider so it can be replaced.

The feature that you are using the DisplayAttribute for enum and models properties is great, but it would be even better if we could create our own provider.
Thomas
Posted on: 14 May 2026 12:33
I have looked at ITelerikStringLocalizer  now and I think you are missunderstanding what I need. 
So I want to clarify that my request is not about UI localization, but about model metadata and value localization.

ITelerikStringLocalizer solves localization of Telerik's built-in UI strings (filter operators, pager text, etc.), but it does not address how Telerik resolves:

  • Enum values rendered in Grid, DropDownList, ComboBox, etc.
  • Property display names (column titles, labels)
  • Any model-driven text

Today, those are resolved via DisplayAttribute and reflection, which introduces several limitations in Blazor WebAssembly:

  • No access to DI
  • No async or runtime logic
  • No tenant/user context
  • No database-backed translations
  • No dynamic language switching without full reload

This creates a gap compared to other libraries (e.g. FluentValidation), where localization can be resolved at runtime through a pluggable provider.

So what I an looking for is a pluggable runtime provider for model metadata and values, separate from UI localization.

ADMIN
Dimo
Posted on: 14 May 2026 12:32

Hi Thomas,

Enum values are a completely separate matter and you are correct that they are not subject to component localization. To customize the display of enum values and other properties, you can use templates such as:

The demand for built-in support for enum localization has been practically non-existent throughout the product history, so the probability of us implementing is also rather low, at least for now.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Thomas
Posted on: 14 May 2026 10:19
Maybe I don't understand what the ITelerikStringLocalizer does or I was not clear with what I need.

I am talking about how Telerik are getting strings for Enum Values, and the DTO Properties when I bind then to a grid, Combobox etc. Telerik are today getting these string from the DisplayAttribute and my impression is that the ITelerikStringLocalizer is not used for this, or am I missing something?
ADMIN
Dimo
Posted on: 14 May 2026 09:57

Hi Thomas,

Our components require a localization mechanism that inherits from ITelerikStringLocalizer. However, you are still quite flexible in retrieving the localization messages from outside a .resx file and use additional custom logic.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Create an account Log In
View
Type
Status
Category