Uh oh!
There was an error while loading. Please reload this page.
[browser][non-icu] HybridGlobalization normalization unblocking APIs that became supported. - #86694
[browser][non-icu] HybridGlobalization normalization unblocking APIs that became supported. #86694ilonatommy wants to merge 4 commits into
HybridGlobalization normalization unblocking APIs that became supported. #86694Conversation
ghost
commented
May 24, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIn non-hybrid globalization we are not supporting nromalization forms: KD and KC.
|
tarekgh
commented
May 24, 2023
Looks you need a small tweak to this fix? |
ilonatommy
commented
May 25, 2023
Drafting till we:
|
ilonatommy
commented
Jun 2, 2023
Closing - normalization is getting reverted with #87007 |
In non-hybrid globalization we are not supporting normalization forms: KD and KC.
In the hybrid mode, both forms are supported and we need them for implemenation of hybrid IDN/ACE mapping.
This PR is changing the public API behavior by enabling both forms on Browser platform. When the HybridGlobalziation (that is an opt-in feature) is switched off and the user is not in InvariantGlobalization mode, they will get PNSE exception when they try to use KD/KC. It is asured by validation in
runtime/src/libraries/System.Private.CoreLib/src/System/Globalization/Normalization.Icu.cs
Line 107 in c368b3d
Contributes to #79989.
@lewing this PR changes the behavior: from failing in the build to failing during runtime when KD/KC forms are used.