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".