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
On some browsers/devices, deep linking will be blocked due to popup blockers. This behaviour is somewhat unpredictable (i.e. IOS Safari has different behaviour when in Private mode, "Allow Popups" enabled/disabled, etc. There also isn't any robust mechanism to detect whether these popups have been blocked.
To complicate things further, whether these deep links are blocked or not may be dependent on the specific dApps implementation (e.g. whether their requests are a direct result of user interaction or autonomously initiated by the dApp, whether they have delays, etc.)
Suggest A Solution
It's not tenable to try to ensure deep links always succeed. Instead, we should optimize for the best case/happy path and provide an obivous fallback/"Try Again" as a Plan B. This is a philisophical shift from the previous implementation (there were some complicated workarounds in place to attempt to serve every possible client, but in practice it ended up providing sub-par UX for everyone).
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered:
Issue to be solved
On some browsers/devices, deep linking will be blocked due to popup blockers. This behaviour is somewhat unpredictable (i.e. IOS Safari has different behaviour when in Private mode, "Allow Popups" enabled/disabled, etc. There also isn't any robust mechanism to detect whether these popups have been blocked.
To complicate things further, whether these deep links are blocked or not may be dependent on the specific dApps implementation (e.g. whether their requests are a direct result of user interaction or autonomously initiated by the dApp, whether they have delays, etc.)
Suggest A Solution
It's not tenable to try to ensure deep links always succeed. Instead, we should optimize for the best case/happy path and provide an obivous fallback/"Try Again" as a Plan B. This is a philisophical shift from the previous implementation (there were some complicated workarounds in place to attempt to serve every possible client, but in practice it ended up providing sub-par UX for everyone).
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: