-
Notifications
You must be signed in to change notification settings - Fork 973
Adjust layout and polish - Ledger Add Funds Dialog #3437
Comments
@jkup to test this out, you can use https://jsfiddle.net/LnwtLckc/5/ to register/unregister the bitcoin: URL handler. you should see the component state change as soon as it's registered/unregistered. |
@diracdeltas would this work for both? Then we can just drop the "Transfer bitcoin" button when the URI is not configured. |
@bradleyrichter that would probably work for the vast majority of cases. the one it doesn't cover is if you use a desktop app to handle bitcoin: URLs, so you can't scan the QR code. the point of showing the payment URL is so that you can copy it into your bitcoin app in this situation. you could still copy the wallet address and manually enter the other payment info. i'm not sure how often this case comes up; i think most people have bitcoin apps with QR code scanners. |
we can link the full URL under the wallet address for this case? |
@bradleyrichter sure |
sorry to be chiming in late. here is what we had prior to rc 1: and here is what we have in rc 1: my view is that what we have in rc 1 is less helpful to the new user (and not that helpful to an existing BTC user). my suggestion is that we stick with the first image above with one change: if the browser does not have a bitcoin URI set, then replaces the "Transfer BTC" button with this text "Scan the QR code above or transfer $X to your Brave wallet." below that, keep the usual "Your Brave wallet address is..." |
closing this since it has been replaced by a new version: |
current:
revised:
cc @jkup
The text was updated successfully, but these errors were encountered: