-
Notifications
You must be signed in to change notification settings - Fork 208
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
Document Browser compatibility of Launch DApps #5583
Comments
I've included a note at top of PSM page that notifies users to turn off their Brave shields before continuing with PSM dapp |
I just got a problem report from a colleague:
I didn't realize there was such a thing as keplr for firefox, let alone for iphone. But there is: https://addons.mozilla.org/en-US/firefox/addon/keplr/ @otoole-brendan do we document supported browsers in https://docs.inter.trade/ ? I'm struggling to find it. |
Re-prioritizing this for Vaults release - we need to be able to say what browsers we support. |
Once this is done we need to QA the dapps on each browser and common configurations. For example, Brave with Shields or Firefox with Tracking Prevention. Whatever diagnostic signals we use will have to be robust to browser changes, such as Chrome's First-Party Sets rollout that broke the wallet bridge: Agoric/dapp-psm#69 |
I have documented supported browsers on Gitbook: https://docs.inter.trade/user-how-to/supported-browsers |
I'd like to do a bit more testing on Firefox before closing ticket though. |
Docs updated. Closing for now - Edge testing required to change - not subject to this ticket - will create another if needed. |
At Launch, unless we implement a different Wallet Connect protocol (#5506), we will only support Firefox and Chromium-based browsers. We should clearly document that on our website, along with any necessary configuration settings such disabling Shields Up in Brave.
If feasible, we should also detect when a Chromium browser has settings that preclude the DAPpps from running correctly, e.g. Brave with Shields Up.
The text was updated successfully, but these errors were encountered: