[release/8.0] Fix incorrect time patterns for some cultures on browser in HybridGlobalization
#103964
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… `HybridGlobalization`
|
Tagging subscribers to this area: @dotnet/area-system-globalization |
kg
approved these changes
Jun 25, 2024
mkhamoyan
approved these changes
Jun 25, 2024
pavelsavara
changed the title
HybridGlobalizationHybridGlobalization
ilonatommy
added
Servicing-approved
ilonatommy
merged commit 5753765
into
dotnet:release/8.0-staging
182 of 191 checks passed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #103804.
This PR makes improvements to values returned in date/time format APIs.
Customer Impact
Yes, if they use
HybridGlobalization, in a few cultures they will see improved format of long date. Reported by a customer in #103745.Regression
No.
Testing, Risk
Low risk, automated testing.