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

[Bug]: Simulation Details reports NumberFormat RangeError for some locales #24067

Closed
dbrans opened this issue Apr 16, 2024 · 1 comment · Fixed by #24068
Closed

[Bug]: Simulation Details reports NumberFormat RangeError for some locales #24067

dbrans opened this issue Apr 16, 2024 · 1 comment · Fixed by #24068
Assignees
Labels
INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. release-11.16.0 Issue or pull request that will be included in release 11.16.0

Comments

@dbrans
Copy link
Contributor

dbrans commented Apr 16, 2024

@anaamolnar reported 3 inquiries of the error “RangeError: Incorrect locale information provided” when attempting a transaction.

RangeError: Incorrect locale information provided
  at Intl.NumberFormat (<anonymous>)
  at chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-6.js:1:286226
  at a.IndividualFiatDisplay (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-7.js:1:392298)
  at ga (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:266221)
  at _l (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:311148)
  at Ru (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:297011)
  at Au (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:296936)
  at Su (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:294276)
  at chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:252626
  at n.unstable_runWithPriority (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-2.js:1:335481)
  at $i (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:252335)
  at eo (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:252571)
  at Zi (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:252506)
  at bu (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:291042)
  at Ra (chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-1.js:33:269878)
  at chrome-extension://ljfoeinjpaedjfecbmggjgodbgkmjkjk/ui-6.js:1:279473
@dbrans dbrans self-assigned this Apr 16, 2024
@metamaskbot metamaskbot added the INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. label Apr 16, 2024
@dbrans
Copy link
Contributor Author

dbrans commented Apr 16, 2024

The following locales are affected: es_419, pt_BR, pt_PT, zh_CN, zh_TW
Basically, exactly those locales that have an underscore.

dbrans added a commit that referenced this issue Apr 17, 2024
#24068)

## **Description**
**Problem:** The locale returned by `getCurrentLocale` is not meant to
be used with the [Intl
API](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl).

**To fix this, this PR will:**
* Rename `getCurrentLocale` => `getLocaleNotSafeForIntl` to alert
developers in the future.
* Add `getIntlLocale` which converts the locale returned from
`getLocaleNotSafeForIntl` into a BCP 47 Language Tag which can be used
with the Intl API.
* Add tests to ensure that `getIntlLocale` works with all our locales
going forward.

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24068?quickstart=1)

## **Related issues**

Fixes: #24067

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@metamaskbot metamaskbot added the release-11.16.0 Issue or pull request that will be included in release 11.16.0 label Apr 17, 2024
dbrans added a commit that referenced this issue Apr 17, 2024
#24068)

## **Description**
**Problem:** The locale returned by `getCurrentLocale` is not meant to
be used with the [Intl
API](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl).

**To fix this, this PR will:**
* Rename `getCurrentLocale` => `getLocaleNotSafeForIntl` to alert
developers in the future.
* Add `getIntlLocale` which converts the locale returned from
`getLocaleNotSafeForIntl` into a BCP 47 Language Tag which can be used
with the Intl API.
* Add tests to ensure that `getIntlLocale` works with all our locales
going forward.

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24068?quickstart=1)

## **Related issues**

Fixes: #24067

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. release-11.16.0 Issue or pull request that will be included in release 11.16.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants