-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Register bitcoin: URI handler #3294
Comments
I created a basic flowchart that will help us to find a solution how to solve this issue. |
Ideas, bugs,... to follow-up issue #4313 |
Info about current implementation can be found here. Video example |
QA NOK (WIP, results will be added to this comment) 1. Send button is disabled when autofill is applied BUG Info video: https://watch.screencastify.com/v/trybQcsTp87hmW3hH6IL 2. Mozzila WEB - OK Opening web Suite results in dialog (yay!) and adding the site into opening options (yay!) Removing sites/settings from Firefox results in a dialogue when site is visited again with option to add the site to settings. When site is removed from handler settings, it does not appear in pop up. 3. Chrome WEB Removing sites/settings from chrome://settings/handlers results in being unable to open the handler with the site (OK). Removed site displays a special icon on the far right side of URL bar, clicking on it opens a dialogue about adding site to URI handler settings (OK). |
QA OK I tried this on Linux and it works as intended in FF (93.0) as well as in Chorme. It is the same as @wendys-cats described. When I first open Suite it correctly asks if I want to add it as a Bitcoin URI handler. If I open any BTC URI link, it opens Suite and a pop-up tells me to go to Suite send form and then it fills up the send from with the info correctly (screenshot below). Info:
Screenshot |
Clicking on a
bitcoin:
URI should open Suite and prefill the inputs if the infromation is available. See https://developer.bitcoin.org/devguide/payment_processing.html#bitcoin-uri and BIP-21 for more details.Registering our own
trezorsuite:
handler is dealt with in #991.The text was updated successfully, but these errors were encountered: