-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Dev olu hardware wallet feature flag #16725
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
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [3857747]
Page Load Metrics (2136 ± 102 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
highlights: |
3857747 to
944c0c8
Compare
Builds ready [944c0c8]
Page Load Metrics (1702 ± 261 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
highlights: |
944c0c8 to
d9af3fe
Compare
Builds ready [d9af3fe]
Page Load Metrics (1259 ± 84 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
highlights: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setLedgerTransportPreference in the metamask-controller should not be called, or should return immediately, if canUseHardwareWallets() is false
Disable Hardware connect buttons if the flag is set. Signed-off-by: Akintayo A. Olusegun <[email protected]>
Signed-off-by: Akintayo A. Olusegun <[email protected]>
Signed-off-by: Akintayo A. Olusegun <[email protected]>
Signed-off-by: Akintayo A. Olusegun <[email protected]>
044c1a6 to
c6c330e
Compare
Signed-off-by: Akintayo A. Olusegun <[email protected]>
1100784 to
ee6652a
Compare
|
This was resolved in #17354 |
Explanation
Put the hardware wallet behind a feature flag and disable/remove ledger, trezor and gridplus connect buttons
Screenshots/Screencaps
Before
After
Manual Testing Steps
HARDWARE_WALLETS_MV3=1Pre-merge author checklist
Pre-merge reviewer checklist
If further QA is required (e.g. new feature, complex testing steps, large refactor), add the
Extension QA Boardlabel.In this case, a QA Engineer approval will be be required.