Blazor Client Side (Wasm), Crashes for Arabic/Farsi Google Chrome Localization

[smj0x]

If you believe you have an issue that affects the security of the platform please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our bug bounty but ONLY if it is reported through email.

Describe the bug

Blazor Client Side (Wasm), Crashes for Arabic/Farsi Google Chrome Localization, when using DateTime even though its converted to string.

there should be a global way in startup file to ignore localizations.

To Reproduce

Steps to reproduce the behavior:

1. Using this version of ASP.NET Core '3.0.100'
2. Run Blazor Client Side Wasm with Arabic or Farsi Google Chrome Localization.
3. Use Datetime.ToShortString(); somewhere.
4. See error

Expected behavior

Not A Valid Calendar for the given culture in F12: Developer Tools -> Console

[Screenshots]

[javiercn]

@smjltd Thanks for contacting us.

This seems like a mono issue in DateTime.ToShortString() we will make sure we route the issue to the right place.

[mkArtakMSFT]

This issue was moved to mono/mono#17363