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
We are using a Chrome Extension to inject our modal into websites. This includes a Swap form with a "Connect Wallet" button using solana-labs/wallet-adapter.
When connecting a standard wallet-adapter wallet (such as Phantom Wallet), things work as expected but when connecting Solflare, the solflare-sdk tries to inject an iframe and fails due to content security policy. CSP blocking fetch requests can be worked around (solana/web3.js Connection accepts custom fetch implementation) but we are not aware of such workaround for iframes.
It would be ideal if it was possible to pass a param in SolflareConfig and avoid the iframe part of the workflow altogether.
The text was updated successfully, but these errors were encountered:
We are using a Chrome Extension to inject our modal into websites. This includes a Swap form with a "Connect Wallet" button using solana-labs/wallet-adapter.
When connecting a standard wallet-adapter wallet (such as Phantom Wallet), things work as expected but when connecting Solflare, the solflare-sdk tries to inject an iframe and fails due to content security policy. CSP blocking fetch requests can be worked around (solana/web3.js Connection accepts custom fetch implementation) but we are not aware of such workaround for iframes.
It would be ideal if it was possible to pass a param in SolflareConfig and avoid the iframe part of the workflow altogether.
The text was updated successfully, but these errors were encountered: