mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-23 09:52:26 +01:00
3bd5d714f7
In the case where the initial spend limit for the `approve` function was set to the maximum amount, editing this value would result in the new limit being silently ignored. The transaction would be submitted with the original max spend limit. This occurred because function to generate the new custom data would look for the expected spend limit in the existing data, then bail if it was not found (and in these cases, it was never found). The reason the value was not found is that it was erroneously being converted to a `Number`. A JavaScript `Number` is not precise enough to represent larger spend limits, so it would give the wrong hex value (after rounding had taken place in the conversion to a floating-point number). The data string is now updated without relying upon the original token value; the new value is inserted after the `spender` argument instead, as the remainder of the `data` string is guaranteed to be the original limit. Additionally, the conversion to a `Number` is now omitted so that the custom spend limit is encoded correctly. Fixes #7915 |
||
|---|---|---|
| .. | ||
| add-token | ||
| confirm-add-suggested-token | ||
| confirm-add-token | ||
| confirm-approve | ||
| confirm-deploy-contract | ||
| confirm-send-ether | ||
| confirm-send-token | ||
| confirm-token-transaction-base | ||
| confirm-transaction | ||
| confirm-transaction-base | ||
| confirm-transaction-switch | ||
| create-account | ||
| first-time-flow | ||
| home | ||
| keychains | ||
| lock | ||
| mobile-sync | ||
| provider-approval | ||
| routes | ||
| send | ||
| settings | ||
| unlock-page | ||
| index.js | ||
| index.scss | ||