Skip to content
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

report(i18n): use LHR locale for toLocaleString #5734

Merged
merged 1 commit into from Aug 1, 2018

Conversation

patrickhulce
Copy link
Collaborator

@patrickhulce patrickhulce commented Jul 26, 2018

another piece of #5719, localize the numbers according to the locale specified in the LHR

note the 0,3 s

image

@paulirish
Copy link
Member

Now that #5746 is in, we'll want a test here that confirms we use whatever locale lookupLocale() fell back to -- also here in .toLocaleString calls, rather then having diff locales for strings and numbers.

@@ -61,7 +64,7 @@ class ReportRenderer {
container.appendChild(this._renderReport(clone));

// put the UIStrings back into original state
ReportRenderer.updateAllUIStrings(clonedStrings);
ReportRenderer.updateAllUIStrings(originalUIStrings);
Copy link
Member

Choose a reason for hiding this comment

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

updated because it was a little confusing with clone being the cloned LHR, while clonedStrings was the clone of the original Util.UIStrings, not the translated strings found in clone :)

@paulirish paulirish force-pushed the i18n_renderer_numbers_locale branch from 51395a6 to 6728655 Compare August 1, 2018 00:14
@paulirish paulirish merged commit 3eb213c into master Aug 1, 2018
@paulirish paulirish deleted the i18n_renderer_numbers_locale branch August 1, 2018 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants