I just updated from 4.0.1 to 4.4 and it broke my gridlayouts. I'm guessing it may have to do with the dependencies.

How do I updte the items listed below? Will this resolve my issue?

Before Update:

After Update:

Hi, 

I am using Kendo blazor component and getting below warning while using all the components.  Please see attached screenshot for snippet.

Warning Message : "Found markup element with unexpected name "TelerikGrid". If this is intended to be a component, add a using directive for its namespace"

Can you tell what namespace should I add in razor file to resolve this issue?

--

Thanks, 

Yash

HI,

the DragClueField when using Drag&Drop only exists for the Grid right now. Why is this attribute not setable for the TreeView also?

Inside the Themebuilder is an AppBar-Component but I can not find any documentation about it !?

I would like to use it but I do not know how !

Hi, how can I display an age column based on birthdate. I have this code that displays no data in the age column

       @Age = DateTime.Now.Year - Person.BirthDateYear

       <GridColumn Field="Age" Title="Age" />

Age is defined in the @Code section:
public int Age;

Thanks

I am encountering a strange issue and wanted to check with the community on what might be going on. When using a NumericTextBox in a blazor client-side (WebAssembly) app, and switching between en-US and es-US locales, we are seeing the textbox use commas as the decimal separator for es-US, but are expecting it to use period (consistent with .NET's behavior when formatting for the es-US culture and with other sources).

The demo here (Blazor NumericTextBox Demos - Globalization | Telerik UI for Blazor) formats numbers the same way when selecting Spanish, and based on the currency symbol it seems clear the formatting is using the es-ES locale (.NET behavior is also consistent with this).

Is there a known issue where the NumericTextBox for Telerik Blazor uses commas as the decimal separator for the es-US locale, or is this possibly a new issue for which we should just create a bug report? Or, perhaps most likely, does this point to us doing something wrong, like maybe setting the culture to just es or something?

If it matters - when the user switches the language in the UI, we are reloading the site and setting CultureInfo.DefaultThreadCurrentCulture and CultureInfo.DefaultThreadCurrentUICulture to a new CultureInfo instance created with name "en-US" or "es-US".