Display hex string for signing when string is not a UTF8 string #10968
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.
When the string is printable we display the string, otherwise we will now display the 0x prefixed hex of the signing data.
Resolves brave/brave-browser#19228
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan:
Clone this:
https://github.com/bbondy/eth-manual-tests
python -m SimpleHTTPServer 8081
Navigate to http://localhost:8081/request.html
Use eth_requestAccounts so you can eth_sign with the test data below.
Here are 3 test cases to try:
0x68656c6c6f20776f726c64
Should produce: hello world
0xdeadbeef
Should produce 0xdeadbeef
Unicode string
0x4120756e69636f646520c68e20737472696e6720c3b1