You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a new browser extension and would like users to be able to login to their Sui wallet from the extension popup and not have to call ConnectButton from a standard browser window.
I've tried multiple configs of my V3 extension manifest, using 'externally_connectable' like so:
Using various configs, I can't get it to connect to the Sui Wallet extension, and am instead seeing the 'Get Started with Sui' heading and text prompting user to install the Sui extension, after clicking the 'Sui Wallet' button that appears on step 2 of the 'Connect Wallet' flow. ( screenshots attached for context )
For more info on how my browser extension will be leveraging both Sui and Walrus, feel free to check out the official public repo here - https://github.com/zanuka/leaderport-core-ui - where I have a detailed readme and docs on the overall vision / plan.
It's open-source and will be free to download, featuring both on- and off-chain functionality. So it would be awesome to be able to have Sui Wallet as my first supported Web3 wallet.
Perhaps there will be other browser extensions that might also want to be able to connect this way as well and your team would find this extension-to-extension communication to be useful. 🤞🏼
Popup - Step 1
Popup - Step 2
Popup - Step 3
Thanks for your time!
The text was updated successfully, but these errors were encountered:
I think directly sending messages to the extension is not something they are planning to support. I think the correct way for this to work would be to allow the wallet inject its content script into any webviews that need to connect to the wallet. Unfortunately, I don't know a lot about chrome extensions myself, and am not sure if/how that could be enabled.
Another option might be to support the stashed wallet instead, since it doesn't require interacting with a browser extension
Thanks @hayes-mysten, much appreciated. I've pivoted my project concept a bit in the meantime and am just focusing on supporting Sui Wallet login via a base 'intermediary' page which works as expected. The more I thought about it, the more the extension-to-extension communication seemed like a feature that users would not enjoy.
New
I'm working on a new browser extension and would like users to be able to login to their Sui wallet from the extension popup and not have to call ConnectButton from a standard browser window.
I've tried multiple configs of my V3 extension manifest, using 'externally_connectable' like so:
Using various configs, I can't get it to connect to the Sui Wallet extension, and am instead seeing the 'Get Started with Sui' heading and text prompting user to install the Sui extension, after clicking the 'Sui Wallet' button that appears on step 2 of the 'Connect Wallet' flow. ( screenshots attached for context )
I think that it will only work if your Sui Wallet extension exposes that particular API option publicly, using "*" wildcard in the
matches[]
array, as stated in Google extensions docs here - https://developer.chrome.com/docs/extensions/reference/manifest/externally-connectableFor more info on how my browser extension will be leveraging both Sui and Walrus, feel free to check out the official public repo here - https://github.com/zanuka/leaderport-core-ui - where I have a detailed readme and docs on the overall vision / plan.
It's open-source and will be free to download, featuring both on- and off-chain functionality. So it would be awesome to be able to have Sui Wallet as my first supported Web3 wallet.
Perhaps there will be other browser extensions that might also want to be able to connect this way as well and your team would find this extension-to-extension communication to be useful. 🤞🏼
Popup - Step 1
Popup - Step 2
Popup - Step 3
Thanks for your time!
The text was updated successfully, but these errors were encountered: