fix(ui): restore login primary action hierarchy - #153
Open
Jdelg718 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Problem
The unloaded login menu intends Load Mnemonic and New Mnemonic to use the orange primary-action style, with Scan and Settings visually secondary.
That hierarchy originally worked when the menu contained Load, New, and Settings. Commit
96d1628later inserted Scan at index 0, but the positionalfor (i = 2; ...)styling cutoff was not updated. The idle menu therefore showed Scan + Load as primary and New + Settings as secondary.Change
Result
Idle unloaded-menu hierarchy:
Entry order, labels, icons, callbacks, geometry, touch behavior, global theme semantics, and wallet/security logic are unchanged.
Verification
clang-format --dry-run --Werror.git diff --checkpasses.Scope
This is intentionally separate from #152. It is a small pre-existing visual hierarchy regression observed during physical
wave_43validation and has no security impact.