Skip to content

Fix virtualization culture invariance #26432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

SteveSandersonMS
Copy link
Member

@SteveSandersonMS SteveSandersonMS commented Sep 29, 2020

Fixes #26424

Description

Blazor's virtualization uses culture-specific formatting (ToString()) when emitting values for css heights. In cultures that use decimal separators for their heights, the generated height is not a valid css value. This change updates the heights to use invariant formatting.

Customer impact

The Virtualize component does not function when executing in non-English locales. This affects both Blazor Server with request localization and Blazor WebAssembly.

Regression

No. The feature is new to .NET 5 RC1.

Risk

The change is isolated to the Virtualize component and was tested manually.

@SteveSandersonMS SteveSandersonMS requested a review from a team as a code owner September 29, 2020 17:47
@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Sep 29, 2020
Copy link
Contributor

@pranavkm pranavkm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops

@pranavkm pranavkm added the Servicing-consider Shiproom approval is required for the issue label Sep 29, 2020
@ghost
Copy link

ghost commented Sep 29, 2020

Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge.

@pranavkm
Copy link
Contributor

I can work on getting this thru tactics.

@Pilchie Pilchie added this to the 5.0.0 milestone Sep 29, 2020
@JamesNK
Copy link
Member

JamesNK commented Sep 29, 2020

We need to get culture analyzers turned on - #24567

@pranavkm pranavkm added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Sep 29, 2020
@pranavkm
Copy link
Contributor

@dotnet/aspnet-build could you merge this?

@pranavkm pranavkm linked an issue Sep 29, 2020 that may be closed by this pull request
@ajaybhargavb ajaybhargavb merged commit 67ac167 into release/5.0 Sep 29, 2020
@ajaybhargavb ajaybhargavb deleted the stevesa/fix-virtualization-culture-invariance branch September 29, 2020 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blazor virtualization does not work properly
6 participants