`HybridGlobalization` doesn't work anymore in aspnetcore 10 RC 1 / Blazor WebAssembly

[ysmoradi]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Discussion link

I used to enable HybridGlobalization in my blazor webassembly projects and I could change culture at runtime programmatically at anytime, but now, in .NET 10 RC 1, it forces me to enable BlazorWebAssemblyLoadAllGlobalizationData, resulting into more additional files download and 150KB (Brotli Compressed) download size )":

Doesn't HybridGlobalization mean it would use browser's data instead of relying on dotnet .dat files as much as possible?

In order to test, try opening https://adminpanel.bitplatform.dev (Would work) and https://todo.bitplatform.dev (Wouldn't work) on non-English browser.

Error:

ManagedError: AggregateException_ctor_DefaultMessage (Blazor detected a change in the application's culture that is not supported with the current project configuration. To change culture dynamically during startup, set <BlazorWebAssemblyLoadAllGlobalizationData>true</BlazorWebAssemblyLoadAllGlobalizationData> in the application's project file.)

Expected Behavior

Creating new CultureInfo() should work with HybridGlobalization just like .NET 9, because browser is providing culture data for all cultures and no need to download additional 150KB

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

10.0.100-rc.1.25451.107

Anything else?

No response

[javiercn]

@ysmoradi thanks for contacting us.

I believe HybridGlobalization was never officially supported and that we decided not to move forward with it as it presented significant drawbacks in some common scenarios.

/cc: @ilonatommy @pavelsavara

[ysmoradi]

So, you mean you've removed it entirely? There's no such a thing anymore? )":

[Kyemate]

@ysmoradi thanks for contacting us.

I believe HybridGlobalization was never officially supported and that we decided not to move forward with it as it presented significant drawbacks in some common scenarios.

/cc: @ilonatommy @pavelsavara

What are the drawbacks with using it?

[pavelsavara]

I believe HybridGlobalization was never officially supported

Correct, it was an experiment.

So, you mean you've removed it entirely? There's no such a thing anymore? )":

Correct. dotnet/runtime#110567

What are the drawbacks with using it?

Drawbacks were

• completeness, the browser API doesn't cover full capabilities of dotnet public APIs. And so we had throw PNSE in the missing cases.
• performance. We had to marshal (copy/encode) each C# string to JS string. Imagine we were doing that for example to sort string array, on each compare operation.
• different behavior on different browsers and versions. Also different from dotnet on desktop. Typically for non-western languages.
• runtime code complexity

GlobalizationNative_GetSortKey was interesting/difficult

[ilonatommy]

@ysmoradi if you would like to limit the size of the globalization data loaded, let's consider some options, described in this doc. You have to find answer to a few questions:

• What languages do you want to support? Are they contained in any of the shards that we're shipping? EFIGS / CJK / no-CJK? Check whitelist contents to define that. If so, use the corresponding <BlazorIcuDataFileName>icudt_{{SHARD_NAME}}.dat</BlazorIcuDataFileName> value in the client project.
• If your app is using cultures from multiple shards, you can either build your own ICU file custom ICU or stick to the full culture download with <BlazorWebAssemblyLoadAllGlobalizationData>true</BlazorWebAssemblyLoadAllGlobalizationData>, as the message suggests.

@javiercn, we could change the message to not only suggest using BlazorWebAssemblyLoadAllGlobalizationData but also point to the globalization docs.

Edit:
The issue for copying the docs from github to learn.microsoft.com: dotnet/AspNetCore.Docs#36155.

[ysmoradi]

Thanks! None of them are match (Due support for Chinese, Arabic and English), but I'd check the custom one.