Merge develop to master following B2CA-1752 #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ragger.firmware.stax has been replaced by ragger.firmware.touch with the introduction of flex device
…ragger-version Bump ragger version
…github-artifact-version Bump actions/upload-artifact and actions/download-artifact version to v4
update version and add provision for stax ragger tests in nano.
…-latest-nbgl-usecase-functions-for-stax Use the guideline provided useCaseHomeAndSettings use case.
Move the ChoiceList __settings as layout
by changing `C_round_warning_64px with `C_Important_Circle_64px` that is similar
- screen contains more data: number of screen reduced - swipe instead of tap - QR button has moved
Position are fixed in Ragger v1.21.0
…tests-update Stax tests update
…support Flex support
If blindsigning is required, show two warning screens , the 2nd being details about the error. Standardize the msgs shown in confirm trasaction/rejection screens using macros.
1. test_basic.py - remove blindsigning settings from settings menu 2. test_blindsign_too_deep.py - Remove blindsign enabled section and consolidate two warning screens in one utils function. 3. test_blindsign_too_deep_rejections.py - Address changes due to two warning screens. Note that first warning screen has reverse confirm/reject buttons 4. test_blindsign_too_large.py - Remove blindsign enabled section. 5. test_parsing_errors.py - add the blindsign warning screen. note that the warning screen has reverse confirm/reject buttons.
info.png is deleted on unrelated golden snapshot generations.
…blindsign-button Change blindsign flow according to guideline.
…ichelson-primitive-D_Ticket Add michelson `D_Ticket` to the formatter
Blindsigning always activated. i.e. if the message to sign is not parsable, alert risk and ask sign without showing precise message's information
From `tinyurl.com/Tezos-ledger` to `bit.ly/ledger-tez`. In order to have the same url on nano device. Change because the old one does not fit properly on nano screens.
To make the flow easier to read
…ard-nano-blindsigning Standard nano blindsigning
…ing-for-stax 254 use usecasestreaming for stax
The reviewStreamingFinish already provides a reject confirmation page.
TZ_SCREEN_LINES + background + left & right arrow + optionnal icon
i.e. PB for our current usage
- ledger-app-builder == 3.30.0 - ragger == 1.21.1 - speculos == 0.9.6
…on-pages-at-last-signing-page 261 duplicate rejection pages at last signing page
…lindsigning-warning-arrows Fix blindsigning warning arrows
…ledger-app-builder-version Bump `ledger-app-builder` version
…ingle page. - fixes trilitech#260
Flex upgrade
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.